Traffic Pattern Parameters in a Handover Procedure of a Wireless Network

ABSTRACT

A first base station receives from a second base station, a handover request message comprising traffic pattern parameters of a wireless device. The traffic pattern parameters comprise a first traffic periodicity, a first timing offset, and a first message size. A handover request acknowledge message indicating at least one periodic resource configuration parameter determined based on the first traffic periodicity is sent to the second base station. A random access preamble associated with a handover of the wireless device is received from the wireless device. The first base station determines a resource block assignment based on the first message size. A control command is transmitted to the wireless device. The control command indicates: activation of radio resources associated with the at least one periodic resource configuration parameter; and the resource block assignment.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/803,834, filed Nov. 3, 2017, which claims the benefit of U.S.Provisional Application No. 62/417,169, filed Nov. 3, 2016, which ishereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present invention.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present invention.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present invention.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present invention.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention.

FIG. 10 is an example data flow diagram as per an aspect of embodimentsof the present disclosure.

FIG. 11 is an example data flow diagram as per an aspect of embodimentsof the present disclosure.

FIG. 12 is an example data flow diagram as per an aspect of embodimentsof the present disclosure.

FIG. 13 is a block diagram illustrating an example SPS radio resourceconfiguration and activation as per an aspect of embodiments of thepresent disclosure.

FIG. 14 is a block diagram illustrating an example aspect of anembodiment of the present disclosure.

FIG. 15 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 16 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation of carrieraggregation. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to signal timing in multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention. As illustrated in thisexample, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1 , guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentinvention. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) mayconsist of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain Slot(s) may include a plurality of OFDM symbols 203.The number of OFDM symbols 203 in a slot 206 may depend on the cyclicprefix length and subcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3 . The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention. FIG. 5A shows an example uplink physical channel.The baseband signal representing the physical uplink shared channel mayperform the following processes. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments. The functions may comprise scrambling,modulation of scrambled bits to generate complex-valued symbols, mappingof the complex-valued modulation symbols onto one or severaltransmission layers, transform precoding to generate complex-valuedsymbols, precoding of the complex-valued symbols, mapping of precodedcomplex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present invention.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1 ,FIG. 2 , FIG. 3 , FIG. 5 , and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, an LTE networkmay include a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (e.g. employing an X2 interface). The basestations may also be connected employing, for example, an S1 interfaceto an EPC. For example, the base stations may be interconnected to theMME employing the S1-MME interface and to the S-G) employing the S1-Uinterface. The S1 interface may support a many-to-many relation betweenMMEs/Serving Gateways and base stations. A base station may include manysectors for example: 1, 2, 3, 4, or 6 sectors. A base station mayinclude many cells, for example, ranging from 1 to 50 cells or more. Acell may be categorized, for example, as a primary cell or secondarycell. At RRC connection establishment/re-establishment/handover, oneserving cell may provide the NAS (non-access stratum) mobilityinformation (e.g. TAI), and at RRC connection re-establishment/handover,one serving cell may provide the security input. This cell may bereferred to as the Primary Cell (PCell). In the downlink, the carriercorresponding to the PCell may be the Downlink Primary Component Carrier(DL PCC), while in the uplink, it may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC), while in theuplink, it may be an Uplink Secondary Component Carrier (UL SCC). AnSCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present invention.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC_CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6 . RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the invention.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the MeNB, and theSecondary Cell Group (SCG) containing the serving cells of the SeNB. Fora SCG, one or more of the following may be applied: at least one cell inthe SCG has a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), is configured with PUCCH resources;when the SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or the maximum number of RLC retransmissionshas been reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: a RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of the SCG are stopped, a MeNB may beinformed by the UE of a SCG failure type, for split bearer, the DL datatransfer over the MeNB is maintained; the RLC AM bearer may beconfigured for the split bearer; like PCell, PSCell may not bede-activated; PSCell may be changed with a SCG change (e.g. withsecurity key change and a RACH procedure); and/or neither a directbearer type change between a Split bearer and a SCG bearer norsimultaneous configuration of a SCG and a Split bearer are supported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied: the MeNB may maintain theRRM measurement configuration of the UE and may, (e.g., based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE; upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so);for UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB; the MeNB and the SeNBmay exchange information about a UE configuration by employing of RRCcontainers (inter-node messages) carried in X2 messages; the SeNB mayinitiate a reconfiguration of its existing serving cells (e.g., PUCCHtowards the SeNB); the SeNB may decide which cell is the PSCell withinthe SCG; the MeNB may not change the content of the RRC configurationprovided by the SeNB; in the case of a SCG addition and a SCG SCelladdition, the MeNB may provide the latest measurement results for theSCG cell(s); both a MeNB and a SeNB may know the SFN and subframe offsetof each other by OAM, (e.g., for the purpose of DRX alignment andidentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signalling may be used for sending requiredsystem information of the cell as for CA, except for the SFN acquiredfrom a MIB of the PSCell of a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention. In Example 1, pTAG comprises PCell,and an sTAG comprises SCell1. In Example 2, a pTAG comprises a PCell andSCell1, and an sTAG comprises SCell2 and SCell3. In Example 3, pTAGcomprises PCell and SCell1, and an sTAG1 includes SCell2 and SCell3, andsTAG2 comprises SCell4. Up to four TAGs may be supported in a cell group(MCG or SCG) and other example TAG configurations may also be provided.In various examples in this disclosure, example mechanisms are describedfor a pTAG and an sTAG. Some of the example mechanisms may be applied toconfigurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the invention may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum is therefore needed for cellularoperators to meet the increasing demand Considering user expectations ofhigh data rates along with seamless mobility, it is beneficial that morespectrum be made available for deploying macro cells as well as smallcells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, can be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA offers an alternative for operators to make use of unlicensedspectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAutilizes at least energy detection to determine the presence or absenceof other signals on a channel in order to determine if a channel isoccupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by UEs; time & frequency synchronizationof UEs.

In an example embodiment, DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the eNBtransmissions can start only at the subframe boundary. LAA may supporttransmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

LBT procedure may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. While nodes may follow such regulatoryrequirements, a node may optionally use a lower threshold for energydetection than that specified by regulatory requirements. In an example,LAA may employ a mechanism to adaptively change the energy detectionthreshold, e.g., LAA may employ a mechanism to adaptively lower theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. In anexample Category 4 LBT mechanism or other type of LBT mechanisms may beimplemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (e.g. LBT without randomback-off) may be implemented. The duration of time that the channel issensed to be idle before the transmitting entity transmits may bedeterministic. In an example, Category 3 (e.g. LBT with random back-offwith a contention window of fixed size) may be implemented. The LBTprocedure may have the following procedure as one of its components. Thetransmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by theminimum and maximum value of N. The size of the contention window may befixed. The random number N may be employed in the LBT procedure todetermine the duration of time that the channel is sensed to be idlebefore the transmitting entity transmits on the channel. In an example,Category 4 (e.g. LBT with random back-off with a contention window ofvariable size) may be implemented. The transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window whendrawing the random number N. The random number N is used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be differentfrom the DL LBT scheme (e.g. by using different LBT mechanisms orparameters) for example, since the LAA UL is based on scheduled accesswhich affects a UE's channel contention opportunities. Otherconsiderations motivating a different UL LBT scheme include, but are notlimited to, multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from aUE perspective may be a continuous transmission from a UE with notransmission immediately before or after from the same UE on the sameCC. In an example, UL transmission burst is defined from a UEperspective. In an example, an UL transmission burst may be defined froman eNB perspective. In an example, in case of an eNB operating DL+UL LAAover the same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. For example, an instant in time may be part ofa DL transmission burst or an UL transmission burst.

In an example, in FIG. 13 , semi-persistent scheduling (SPS)configuration may be employed to assign uplink and/or sidelink resourcesfor periodic traffic of a UE. By assigning periodic resources with SPSconfiguration, a UE may not need to request uplink and/or sidelinkresources to a base station whenever packets of periodic traffic aregenerated. The SPS configuration may reduce signaling between a basestation and a wireless device for resource allocation if traffic of thewireless device is periodic. The SPS configuration may compriseperiodicity information of allocated radio resources.

In an example, a base station may assign SPS radio resources via a radioresource control (RRC) message to a wireless device. One or moreparameters of the RRC message may comprise a periodicity of the SPSradio resources. The base station may activate the SPS radio resourcesassigned via the RRC message by transmitting a DCI activation indicationto the wireless device. The wireless device may be able to use the SPSradio resources periodically after k time duration from the DCIactivation indication without further resource allocation request untilthe SPS radio resources are deactivated.

In an example embodiment, various DCI formats may be used for SPSscheduling. For example, the DCI format 0 may be used for uplink SPS. Inan example, the fields for DCI format 0 may comprise one or more of thefollowing fields:

-   -   Carrier indicator—0 or 3 bits.    -   Flag for format0/format1A differentiation—1 bit, where value 0        may indicate format 0 and value 1 may indicate format 1A.    -   Frequency hopping flag—1 bit. This field may be used as the MSB        of the corresponding resource allocation field for resource        allocation type 1.    -   Resource block assignment and hopping resource allocation—┌log₂        (N_(RB) ^(UL)(N_(RB) ^(UL)+1)/2)┐ bits where N_(RB) ^(UL) may be        the uplink bandwidth configuration number of resource blocks.    -   Modulation and coding scheme and redundancy version—5 bits    -   New data indicator—1 bit    -   TPC command for scheduled PUSCH—2 bits    -   Cyclic shift for DM RS and OCC index—3 bits    -   UL index—2 bits (this field may be present only for TDD        operation with uplink-downlink configuration 0)    -   Downlink Assignment Index (DAI)—2 bits (this field may be        present only for cases with TDD primary cell and either TDD        operation with uplink-downlink configurations 1-6 or FDD        operation)    -   CSI request—1, 2 or 3 bits. The 2-bit field may apply to UEs        configured with no more than five DL cells and to UEs that are        configured with more than one DL cell and when the corresponding        DCI format is mapped onto the UE specific search space given by        the C-RNTI, UEs that are configured by higher layers with more        than one CSI process and when the corresponding DCI format is        mapped onto the UE specific search space given by the C-RNTI,        UEs that are configured with two CSI measurement sets by higher        layers with the parameter csi-MeasSubframeSet, and when the        corresponding DCI format is mapped onto the UE specific search        space given by the C-RNTI; the 3-bit field may apply to the UEs        that are configured with more than five DL cells and when the        corresponding DCI format is mapped onto the UE specific search        space given by the C-RNTI; otherwise the 1-bit field applies    -   SRS request—0 or 1 bit. This field may only be present in DCI        formats scheduling PUSCH which are mapped onto the UE specific        search space given by the C-RNTI.    -   Resource allocation type—1 bit. This field may only be present        if N_(RB) ^(UL)≤N_(RB) ^(DL) where N_(RB) ^(UL) may be the        uplink bandwidth configuration in number of resource blocks and        N_(RB) ^(DL) may be the downlink bandwidth configuration in        number of resource blocks.

If the number of information bits in format 0 mapped onto a given searchspace is less than the payload size of format 1A for scheduling the sameserving cell and mapped onto the same search space (including anypadding bits appended to format 1A), zeros may be appended to format 0until the payload size equals that of format 1A.

A UE may validate a Semi-Persistent Scheduling assignment PDCCH if allthe following conditions are met: the CRC parity bits obtained for thePDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI;and the new data indicator field is set to ‘0’. In case of DCI formats2, 2A, 2B, 2C and 2D, the new data indicator field may refer to the onefor the enabled transport block.

A UE may validate a Semi-Persistent Scheduling assignment EPDCCH if allthe following conditions are met: the CRC parity bits obtained for theEPDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI;and the new data indicator field is set to ‘0’. In case of DCI formats2, 2A, 2B, 2C and 2D, the new data indicator field may refer to the onefor the enabled transport block.

Validation may be achieved if the fields for the respective used DCIformat are set according to various values. For example, if validationis achieved, the UE may consider the received DCI informationaccordingly as a valid semi-persistent activation or release. Ifvalidation is not achieved, the received DCI format may be considered bythe UE as having been received with a non-matching CRC.

For the case that the DCI format indicates a semi-persistent downlinkscheduling activation, the TPC command for PUCCH field may be used as anindex to one of the four PUCCH resource values configured by higherlayers, with the mapping defined as followings. If a value of TPCcommand for PUCCH is ‘00’, the first PUCCH resource value may beconfigured by the higher layers. If a value of TPC command for PUCCH is‘01’, the second PUCCH resource value may be configured by the higherlayers. If a value of TPC command for PUCCH is ‘10’, the third PUCCHresource value may be configured by the higher layers. If a value of TPCcommand for PUCCH is ‘11’, the fourth PUCCH resource value may beconfigured by the higher layers.

In an example, the information element SPS-Config may be used by RRC tospecify the semi-persistent scheduling configuration.

In an example, multiple downlink or uplink SPS may be configured for acell. In an example, multiple SPS RNTI may be configured when aplurality of SPS is configured. In an example, RRC may comprise an indexidentifying an SPS configuration for a cell. In an example, the DCIemploying SPS RNTI and triggering an SPS may include the index of theSPS that is triggered (initialized) or released.

In an example, SPS configuration may include MCS employed for packettransmission of an MCS grant. In an example, implicitReleaseAfter may bethe number of empty transmissions before implicit release. Value e2 maycorresponds to 2 transmissions, e3 may correspond to 3 transmissions andso on. In an example, n1PUCCH-AN-PersistentList,n1PUCCH-AN-PersistentListP1 may be the List of parameter: n_(PUCCH)^((1,p)) for antenna port P0 and for antenna port P1 respectively. Fieldn1-PUCCH-AN-PersistentListP1 may be applicable only if thetwoAntennaPortActivatedPUCCH-Format1a1b in PUCCH-ConfigDedicated-v1020is set to true. Otherwise the field may not be configured. In anexample, numberOfConfSPS-Processes may be the number of configured HARQprocesses for Semi-Persistent Scheduling.

In an example, p0-NominalPUSCH-Persistent may be the parameter:P_(O_NOMINAL_PUSCH) (0) used in PUSCH power control with unit in dBm andstep 1. This field may be applicable for persistent scheduling. Ifchoice setup is used and p0-Persistent is absent, the value ofp0-NominalPUSCH for p0-NominalPUSCH-Persistent may be applied. If uplinkpower control subframe sets are configured by tpc-SubframeSet, thisfield may apply for uplink power control subframe set 1.

In an example, p0-NominalPUSCH-PersistentSubframeSet2 may be theparameter: P_(O_NOMINAL_PUSCH) (0) used in PUSCH power control with unitin dBm and step 1. This field may be applicable for persistentscheduling, only. If p0-PersistentSubframeSet2-r12 is not configured,the value of p0-NominalPUSCH-SubframeSet2-r12 may be applied forp0-NominalPUSCH-PersistentSubframeSet2. E-UTRAN may configure this fieldonly if uplink power control subframe sets are configured bytpc-SubframeSet, in which case this field may apply for uplink powercontrol subframe set 2.

In an example, p0-UE-PUSCH-Persistent may be the parameter:P_(O_UE_PUSCH) (0) used in PUSCH power control with unit in dB. Thisfield may be applicable for persistent scheduling, only. If choice setupis used and p0-Persistent is absent, the value of p0-UE-PUSCH may beapplied for p0-UE-PUSCH-Persistent. If uplink power control subframesets are configured by tpc-SubframeSet, this field may be applied foruplink power control subframe set 1.

In an example, p0-UE-PUSCH-PersistentSubframeSet2 may be the parameter:P_(O_UE_PUSCH) (0) used in PUSCH power control with unit in dB. Thisfield may be applicable for persistent scheduling, only. Ifp0-PersistentSubframeSet2-r12 is not configured, the value ofp0-UE-PUSCH-SubframeSet2 may be applied forp0-UE-PUSCH-PersistentSubframeSet2. E-UTRAN may configure this fieldonly if uplink power control subframe sets are configured bytpc-SubframeSet, in which case this field may apply for uplink powercontrol subframe set 2.

In an example, semiPersistSchedC-RNTI may be Semi-Persistent SchedulingC-RNTI. In an example, semiPersistSchedIntervalDL may be Semi-persistentscheduling interval in downlink Its value may be in number ofsub-frames. Value sf10 may correspond to 10 sub-frames, sf20 maycorrespond to 20 sub-frames and so on. For TDD, the UE may round thisparameter down to the nearest integer (of 10 sub-frames), e.g. sf10 maycorrespond to 10 sub-frames, sf32 may correspond to 30 sub-frames, sf128may correspond to 120 sub-frames.

In an example, semiPersistSchedIntervalUL may be semi-persistentscheduling interval in uplink. Its value in number of sub-frames. Valuesf10 may correspond to 10 sub-frames, sf20 may correspond to 20sub-frames and so on. For TDD, the UE may round this parameter down tothe nearest integer (of 10 sub-frames), e.g. sf10 may correspond to 10sub-frames, sf32 may correspond to 30 sub-frames, sf128 may correspondto 120 sub-frames. In an example, twoIntervalsConfig may be trigger oftwo-intervals-Semi-Persistent Scheduling in uplink. If this field ispresent, two-intervals-SPS is enabled for uplink. Otherwise,two-intervals-SPS is disabled.

In an example, when Semi-Persistent Scheduling is enabled by RRC, theinformation such as, for example, may be provided: Semi-PersistentScheduling C-RNTI; Uplink Semi-Persistent Scheduling intervalsemiPersistSchedIntervalUL and number of empty transmissions beforeimplicit release implicitReleaseAfter, if Semi-Persistent Scheduling isenabled for the uplink; Whether twoIntervalsConfig is enabled ordisabled for uplink, only for TDD; and Downlink Semi-PersistentScheduling interval semiPersistSchedIntervalDL and number of configuredHARQ processes for Semi-Persistent Scheduling numberOfConfSPS-Processes,if Semi-Persistent Scheduling is enabled for the downlink

In an example, when Semi-Persistent Scheduling for uplink or downlink isdisabled by RRC, the corresponding configured grant or configuredassignment may be discarded.

In an example, Semi-Persistent Scheduling may be supported on the SpCellin release 13 LTE. In an example, Semi-Persistent Scheduling may not besupported for RN communication with the E-UTRAN in combination with anRN subframe configuration.

In an example, when eIMTA is configured for the SpCell, if a configureduplink grant or a configured downlink assignment occurs on a subframethat can be reconfigured through eIMTA L1 signalling, the UE behaviormay be left unspecified.

In an example, after a Semi-Persistent downlink assignment isconfigured, the MAC entity may consider sequentially that the Nthassignment occurs in the subframe for which:(10*SFN+subframe)=[(10*SFNstart time+subframestarttime)+N*semiPersistSchedIntervalDL] modulo 10240, where SFNstart timeand subframestart time may be the SFN and subframe, respectively, at thetime the configured downlink assignment was (re-)initialized.

In an example, after a Semi-Persistent Scheduling uplink grant isconfigured, the MAC entity may: if twoIntervalsConfig is enabled byupper layer: set the Subframe_Offset according to Table below. else: setSubframe_Offset to 0.

In an example, it may be considered sequentially that the Nth grantoccurs in the subframe for which: (10*SFN+subframe)=[(10*SFNstarttime+subframestart time)+N*semiPersistSchedIntervalUL+Subframe_Offset*(Nmodulo 2)] modulo 10240, where SFNstart time and subframestart time maybe the SFN and subframe, respectively, at the time the configured uplinkgrant was (re-)initialised.

In an example, subframe_offset values may be configured with threefields: TDD UL/DL configuration, Position of initial Semi-Persistentgrant, and/or subframe-offset value (ms). In an example, differentconfigurations for the three fields may be defined, e.g. (0, N/A, 0),(1, Subframes 2 and 7, 1), (1, Subframes 3 and 8, −1), (2, Subframe 2,5), (2, Subframe 7, −5), (3, Subframes 2 and 3, 1), (3, Subframe 4, −2),(4, Subframe 2, 1), (4, Subframe 3, −1), (5, N/A, 0), and (6, N/A, 0).

In an example, the MAC entity may clear the configured uplink grantimmediately after implicitReleaseAfter number of consecutive new MACPDUs containing zero MAC SDUs have been provided by the Multiplexing andAssembly entity, on the Semi-Persistent Scheduling resource.Retransmissions for Semi-Persistent Scheduling may continue afterclearing the configured uplink grant. In an example, the IEMAC-MainConfig may be used to specify the MAC main configuration forsignalling and data radio bearers. In an example, the MAC mainconfiguration parameters may be configured independently per Cell Group(e.g., MCG or SCG), unless explicitly specified otherwise.

In an example, MAC-MainConfig information element may be configured.

In an example, dl-PathlossChange may indicate DL Pathloss Change and thechange of the required power backoff due to power management (as allowedby P-MPRc) for PHR reporting. Its value may be in dB. Value dB1 maycorrespond to 1 dB, dB3 may correspond to 3 dB and so on. The same valuemay apply for serving cell (although the associated functionality may beperformed independently for cell).

In an example, drx-Config may be used to configure DRX. E-UTRAN mayconfigure the values in DRX-Config-v1130 only if the UE indicatessupport for IDC indication. E-UTRAN may configure drx-Config-v1130,drx-Config-v1310 and drx-Config-r13 if drx-Config (without suffix) isconfigured. E-UTRAN may configure drx-Config-r13 only if UE supports CE.

In an example, drx-InactivityTimer may be a timer for DRX. Its value maybe in number of PDCCH sub-frames. Value psf1 may correspond to 1 PDCCHsub-frame, psf2 may correspond to 2 PDCCH sub-frames and so on.

In an example, drx-RetransmissionTimer may be a timer for DRX. Its valuemay be in number of PDCCH sub-frames. Value psf1 may correspond to 1PDCCH sub-frame, psf2 may correspond to 2 PDCCH sub-frames and so on. Incase drx-RetransmissionTimer-v1130 or drx-RetransmissionTimer-v1310 issignalled, the UE may ignore drx-RetransmissionTimer (e.g. withoutsuffix).

In an example, drx-ULRetransmissionTimer may be a timer for DRX. Itsvalue may be in number of PDCCH sub-frames. Value psf0 may correspond tono retransmission timer, value psf1 may correspond to 1 PDCCH sub-frame,psf2 may correspond to 2 PDCCH sub-frames and so on.

In an example, drxShortCycleTimer may be a timer for DRX. Its value maybe in multiples of shortDRX-Cycle. A value of 1 may correspond toshortDRX-Cycle, a value of 2 may corresponds to 2*shortDRX-Cycle and soon.

In an example, dualConnectivityPHR may indicate if power headroom may bereported using Dual Connectivity Power Headroom Report MAC ControlElement. If PHR functionality and dual connectivity are configured,E-UTRAN may configure the value setup for this field and configuresphr-Config and dualConnectivityPHR for both CGs.

In an example, e-HARQ-Pattern may be configured. In an example, TRUE mayindicate that enhanced HARQ pattern for TTI bundling is enabled for FDD.E-UTRAN may enable this field only when ttiBundling is set to TRUE.eDRX-Config-CycleStartOffset may indicate longDRX-Cycle anddrxStartOffset. The value of longDRX-Cycle may be in number ofsub-frames. The value of drxStartOffset, in number of subframes, may beindicated by the value of eDRX-Config-CycleStartOffset multiplied by2560 plus the offset value configured in longDRX-CycleStartOffset.E-UTRAN may only configure value setup when the value inlongDRX-CycleStartOffset is sf2560.

In an example, extendedBSR-Sizes may be configured. If value setup isconfigured, the BSR index may indicate extended BSR size levels.extendedPHR may indicate if power headroom may be reported using theExtended Power Headroom Report MAC control element. E-UTRAN mayconfigure the value setup if more than one and up to eight ServingCell(s) with uplink is configured and none of the serving cells withuplink configured has a servingCellIndex higher than seven and if PUCCHon SCell is not configured and if dual connectivity is not configured.E-UTRAN may configure extendedPHR if phr-Config is configured. The UEmay release extendedPHR if phr-Config is released.

In an example, extendedPHR2 may indicate if power headroom may bereported using the Extended Power Headeroom Report 2 MAC Control Element(value setup). E-UTRAN may configure the value setup if any of theserving cells with uplink configured has a servingCellIndex higher thanseven or if PUCCH SCell (with any number of serving cells with uplinkconfigured) is configured. E-UTRAN may configure extendedPHR2 ifphr-Config is configured. The UE may release extendedPHR2 if phr-Configis released.

In an example, logicalChannelSR-ProhibitTimer timer may be used to delaythe transmission of an SR for logical channels enabled bylogicalChannelSR-Prohibit. Value sf20 may correspond to 20 subframes,sf40 may correspond to 40 subframes, and so on.

In an example, longDRX-CycleStartOffset may be longDRX-Cycle anddrxStartOffset unless eDRX-Config-CycleStartOffset is configured. Thevalue of longDRX-Cycle may be in number of sub-frames. Value sf10 maycorrespond to 10 sub-frames, sf20 may correspond to 20 sub-frames and soon. If shortDRX-Cycle is configured, the value of longDRX-Cycle may be amultiple of the shortDRX-Cycle value. The value of drxStartOffset may bein number of sub-frames. In case longDRX-CycleStartOffset-v1130 issignalled, the UE may ignore longDRX-CycleStartOffset (e.g., withoutsuffix).

In an example, maxHARQ-Tx may be the maximum number of transmissions forUL HARQ.

In an example, onDurationTimer may be a timer for DRX. Its value may bein number of PDCCH sub-frames. Value psf1 may correspond to 1 PDCCHsub-frame, psf2 may correspond to 2 PDCCH sub-frames and so on. In caseonDurationTimer-v1310 is signalled, the UE may ignore onDurationTimer(e.g. without suffix).

In an example, periodicBSR-Timer may be a timer for BSR reporting. Itsvalue may be in number of sub-frames. Value sf10 may correspond to 10sub-frames, sf20 corresponds to 20 sub-frames and so on. In an example,periodicPHR-Timer timer may be for PHR reporting. Its value may be innumber of sub-frames. Value sf10 may correspond to 10 subframes, sf20may correspond to 20 subframes and so on. In an example, phr-ModeOtherCGmay indicate the mode (e.g. real or virtual) used for the PHR of theactivated cells that are part of the other Cell Group (e.g. MCG or SCG),when DC is configured.

In an example, prohibitPHR-Timer timer may be for PHR reporting. Itsvalue may be in number of sub-frames. Value sf0 may correspond to 0subframes, sf100 may correspond to 100 subframes and so on. In anexample, retxBSR-Timer timer may be for BSR reporting. Its value may bein number of sub-frames. Value sf640 may corresponds to 640 sub-frames,sf1280 may correspond to 1280 sub-frames and so on. In an example,sCellDeactivationTimer may be SCell deactivation timer. Its value may bein number of radio frames. Value rf4 may correspond to 4 radio frames,value rf8 may correspond to 8 radio frames and so on. Other values ofdeactivation timer values may be supported, for example, 512, 1024subframes. E-UTRAN may configure the field if the UE is configured withone or more SCells other than the PSCell and PUCCH SCell. If the fieldis absent, the UE may delete any existing value for this field andassume the value to be set to infinity. The same value may apply forSCell of a Cell Group (e.g. MCG or SCG) (although the associatedfunctionality may be performed independently for SCell). FieldsCellDeactivationTimer may not apply for the PUCCH SCell.

In an example, shortDRX-Cycle may be short DRX cycle. Its value may bein number of sub-frames. Value sf2 may correspond to 2 sub-frames, sf5may correspond to 5 subframes and so on. In case shortDRX-Cycle-v1130 issignalled, the UE may ignore shortDRX-Cycle (e.g. without suffix). ShortDRX cycle may not be configured for UEs in CE.

In an example, sr-ProhibitTimer may be timer for SR transmission onPUCCH. Its value may be in number of SR period(s) of shortest SR periodof any serving cell with PUCCH. Value 0 may mean no timer for SRtransmission on PUCCH is configured. Value 1 may correspond to one SRperiod, Value 2 may correspond to 2*SR periods and so on.

In an example, stag-Id may indicate the TAG of an SCell. It may Uniquelyidentify the TAG within the scope of a Cell Group (e.g., MCG or SCG). Ifthe field is not configured for an SCell (e.g. absent inMAC-MainConfigSCell), the SCell may be part of the PTAG.

In an example, stag-ToAddModList, stag-ToReleaseList may be used toconfigure one or more STAGs. E-UTRAN may ensure that a STAG contains atleast one SCell with configured uplink. If, due to SCell release areconfiguration would result in an ‘empty’ TAG, E-UTRAN may includerelease of the concerned TAG. A timeAlignmentTimerSTAG may indicate thevalue of the time alignment timer for an STAG.

In an example, ttiBundling may be configured. TRUE may indicate that TTIbundling is enabled while FALSE may indicate that TTI bundling isdisabled. TTI bundling may be enabled for FDD and for TDD forconfigurations 0, 1 and 6. The functionality may be performedindependently per Cell Group (e.g., MCG or SCG). E-UTRAN may notconfigure TTI bundling for the SCG. For a TDD PCell, E-UTRAN may notsimultaneously enable TTI bundling and semi-persistent scheduling inthis release of the specification. For a Cell Group, E-UTRAN may notsimultaneously configure TTI bundling and SCells with configured uplink,and E-UTRAN may not simultaneously configure TTI bundling and eIMTA.

In an example, a UE may be configured with semi-persistent scheduling ona secondary cell. The eNB may activate semi-persistent scheduling on asecondary cell by sending a PDCCH with semi-persistent schedulingdownlink assignment or semi-persistent scheduling uplink grant on thesecondary cell or on a serving cell scheduling the secondary cell.

In an example, a maximum of one downlink SPS and/or one uplink SPS maybe configured for the PCell. Configuration of multiple SPSs are notsupported for the PCell or any other cell. An SPS C-RNTI is configuredfor the UE to support one DL SPS configuration and/or one UL SPSconfiguration.

In an example, SPS configurations may be used for transmission ofvarious V2X traffic and/or voice traffic by a UE. In an example, a UEsupporting V2X may need to support multiple uplink SPS configurationsfor transmitting various periodic (or semi-periodic) traffic and/orvoice traffic in the uplink. Other examples may be provided. Forexample, CAM messages in V2X may be semi-periodic. In some scenarios,CAM message generation may be dynamic in terms of size, periodicity andtiming. Such changes may result in misalignment between SPS timing andCAM timing. There may be some regularity in size and periodicity betweendifferent triggers. Enhanced SPS mechanisms may be beneficial totransmit V2X traffic, voice traffic, and/or the like. In an example,various SPS periodicity, for example 100 ms and 1 s may be configured.

In an example, multiple SPS configurations may be configured for UUand/or PC5 interface. An eNB may configure multiple SPS configurationsfor a given UE. In an example, SPS configuration specific MCS (e.g. MCSas a part of the RRC SPS-configuration) and/orSPS-configuration-specific periodicity may be configured. Some of theSPS configuration parameters may be the same across multiple SPS andsome other SPS configuration parameters may be different across SPSconfigurations. The eNB may dynamically trigger/release the differentSPS-configurations employing (E)PDCCH DCIs. In an example, the multipleSPS configurations may be indicated by eNB RRC signaling. The dynamicaltriggering and releasing may be performed by eNB transmitting (E)PDCCHDCI to the UE employing SPS C-RNTI.

In an example embodiment, a UE may indicate to an eNB that the UE doesnot intend and/or intend to transmit data before a transmissionassociated to an SPS configuration. The eNB may acknowledge the UEindication.

In an example, an eNB may provide one or more SPS configurations for theUE via RRC signaling. When the UE to start transmitting a type ofmessage employing SPS, the UE may report information about the messageto the eNB, e.g. message type, logical channel, traffic size, SPS index,and/or traffic type, etc. The eNB may transmit an SPS transmission grantbased on the report and provide an SPS grant for a configuration andradio resources. After receiving the grant, the UE may initialize thecorresponding SPS configuration and may transmit the data via the radioresources allocated to the UE.

In an example, multiple SPSs may be active in parallel. For example, anew service may be triggered while the previous service is on-going. Inan example, the UE may indicate the new messages to the serving eNB. TheeNB may provide another transmission grant for the newservice/message(s). The UE may choose another SPS configuration andselect the resources. In an example, the previous SPS grant and the newSPS grant may continue in parallel.

In an example, SPS may be employed for the transmission of BSM, DENMsand CAMs. For example, the UE's speed/position/direction changes withina range. BSM may be periodic traffic with a period of 100 ms. Themessage size of BSM may be in the range of 132˜300 Bytes withoutcertificate and 241˜409 Bytes with certificate. DENMs, once triggered,may be transmitted periodically with a given message period which mayremain unchanged. The message size of the DENM may be 200˜1200 Bytes. Ifthe UE's speed/position/direction does not change or only changes withina small range, the CAM generation periodicity may be fixed.

In an example, the SPS may be supported for the UL and DL VoIPtransmission. In the current SPS specification, the eNodeB may configureSPS periodicity via dedicated RRC signaling. The periodicity of VoIPpacket is generally fixed. The UE may transmit multiple V2X services,which may require different periodicity and packet sizes. The SPS TBsize and period may be adapted to different V2X services. Multipleparallel SPS processes may be activated at the UE. The SPS processes maydiffer in the amount of resource blocks (RBs) allocated and/or SPSperiod and may correspond to different types of V2X packets. Once the ASlayer of UE receives the V2X packets from upper layer, the UE maytrigger V2X packet transmissions on the corresponding SPS grant.Multiple UL SPS configurations may be configured for the UE.

In an example, the eNB may configure different SPS C-RNTIs for differentSPS processes of the UE. The legacy SPS activation and release mechanismmay be reused. Based on the different SPS C-RNTIs, the eNB may triggerwhich SPS process is activated or released. In an exampleimplementation, in order to support multiple SPS configurations adifferent SPS C-RNTI may be configured for different SPS traffic. Forexample, a first SPS C-RNTI may be configured for SPS configuration totransmit voice traffic, a second SPS C-RNTI may be configured for SPSconfiguration to transmit a V2X traffic. An eNB may transmit one or moreRRC messages comprising multiple SPS configuration parameters. Themultiple SPS configuration parameters may comprise multiple SPS-RNTIparameters for multiple SPS configurations (e.g. multiple UL SPSconfigurations).

In an example, a UE configured with multiple SPS C-RNTIs may need tomonitor search space of PDCCH for multiple SPS C-RNTIs, this mechanismmay increase UE processing requirements and/or power consumption. Thereis a need to improve eNB and UE implementation and enhance networkperformance when multiple SPSs are configured for a given UE. Some ofthe example embodiments may implement multiple SPS C-RNTI, and some mayimplement a single SPS C-RNTI.

In an example embodiment, when multiple SPS grant types are configuredfor a UE, for example, when multiple SPS-ConfigUL are configured on acell or when multiple SPS grant types are configured within anSPS-ConfigUL, RRC configuration parameters may comprise an index (may becalled SPS index, SPS identifier, SPS parameter, or any other name)Multiple uplink SPSs parameters may be assigned to (associated with) thesame SPS C-RNTI. A different SPS configuration (e.g. having differentperiods) may be assigned to the same SPS C-RNTI, and may be identifiedby different SPS indexes. The example mechanism may also be applied toDL and/or Sidelink SPS configurations. In example embodiment, multipleSPS configurations (e.g. multiple periodicity, MCS, and/or otherparameters) may be triggered employing the same SPS C-RNTI.

In an example, SPS-ConfigUL1 may be assigned SPS C-RNTI and SPS-index1,and SPS-ConfigUL2 may be assigned SPS C-RNTI and SPS-Index2. An eNB maytransmit one or more RRC messages comprising configuration parameters ofone or more cells (e.g. PCell and/or SCell(s)). The configurationparameters may include configuration parameters for a plurality of SPSs.The configuration parameters may comprise the SPS C-RNTI, SPS-index1 andSPS-index2.

In an example, SPS-ConfigUL may be assigned SPS C-RNTI and may compriseSPS-index1 and SPS-Index2. One or more first SPS configurationparameters may be associated with SPS-index1 and one or more second SPSconfiguration parameters may be associated with SPS-Index2. Example ofSPS configuration parameters maybe periodicity, MCS, grant size, and/orany other SPS configuration parameter presented in RRC SPSconfiguration. An eNB may transmit one or more RRC messages comprisingconfiguration parameters of one or more cells (e.g. PCell and/orSCell(s)). The configuration parameters may include configurationparameters for SPSs. The configuration parameters may comprise the SPSC-RNTI, SPS-index1 and SPS-index2.

In an example, the UE configured with SPS configurations may monitorPDCCH and search for a DCI associated with the SPS C-RNTI (e.g.scrambled with SPS-CRNTI). The eNB may transmit a DCI associated to SPSC-RNTI to the UE to activate or release a SPS grant. The UE may decode aDCI associated with the SPS C-RNTI. The DCI may comprise one or morefields comprising information about the grant. The DCI may furthercomprise an SPS index. The SPS index may determine which one of the SPSconfigurations are activated or released.

Example fields in the DCI grants for an SPS in a legacy system ispresented in the specifications. Many of fields are marked by N/A. In anexample embodiment, one of the existing fields (e.g. one of the N/Afields), or a new field may be introduced in a DCI for configuration ofthe SPS index. A field in the DCI may identify which one of the SPSconfigurations is activated or released. The UE may transmit or receivedata according the grant and SPS configuration parameters.

In an example embodiment, a wireless device may receive at least onemessage comprising: a semi-persistent scheduling (SPS) cell radionetwork temporary identifier (C-RNTI); a first SPS configurationparameter(s); a second SPS configuration parameter(s); a first indexvalue associated with the first SPS configuration parameters; and asecond index value associated with the second SPS configurationparameters. The wireless device may receive a downlink controlinformation (DCI) associated with the SPS C-RNTI. The DCI comprises oneor more fields of an SPS grant and an index value. The wireless devicemay transmit/receive SPS traffic on radio resources identified in theSPS grant considering the SPS configuration parameters associated withthe index value. The SPS configuration parameter associated with theindex may include, for example, SPS periodicity, MCS, radio resourceparameters, and/or other SPS parameters included in SPS configurations.

In an example, the index may be implicitly configured. SPSconfigurations may include a sequence of various options for aparameter. An index of a parameter may be the order of the parameter inthe sequence. In an example embodiment, a wireless device may receive atleast one message comprising: a semi-persistent scheduling (SPS) cellradio network temporary identifier (C-RNTI); SPS configurationparameters; a sequence of a plurality of SPS parameter, e.g.periodicities. An SPS periodicity value may be identified by aperiodicity index. The wireless device may receive a downlink controlinformation (DCI) associated with the SPS C-RNTI. The DCI may compriseone or more fields of an SPS grant and a first periodicity index value.The wireless device may transmit/receive SPS traffic on radio resourcesidentified in the SPS grant considering the SPS configurationparameters, and a first periodicity associated with the firstperiodicity index value. This embodiment may be employed when one ormore SPS C-RNTI is configured. A given SPS traffic (message type) may betransmitted with various periodicity depending on vehicle speed or otherparameters. This mechanism enables updating SPS grant periodicity withthe need for reconfiguring SPS grants. A set of one or more RRCconfiguration parameters may be applicable to different SPSperiodicities. The example embodiment may be extended to otherparameters such as RBs, MCS, and others.

In an example, the SPS DCI may include the SPS grant periodicity,instead of the index value for the periodicity. Since a large number ofperiodicities may be supported. This embodiment may increase the size ofDCI, but may reduce the size of the SPS RRC configuration.

In an example embodiment, an SPS grant may be for a specific messagetype. In current mechanisms, a DCI grant does not comprise informationon traffic types associated with the grant. In an example embodiment, awireless device may receive at least one message comprising: asemi-persistent scheduling (SPS) cell radio network temporary identifier(C-RNTI); a first SPS configuration parameters; a second SPSconfiguration parameters; a traffic index value associated with thefirst SPS configuration parameters; and/or a traffic index valueassociated with the second SPS configuration parameters. The index forthe traffic type may be a logical channel identifier, bearer identifier,V2X traffic type identifier, and/or the like. The identifier may alsodetermine a relative priority of the traffic type compared with othertraffics. The wireless device may receive a downlink control information(DCI) associated with the SPS C-RNTI. The DCI may comprise one or morefields of an SPS grant and a traffic index value (LCI, beareridentifier, V2X traffic type identifier, and/or the like). The wirelessdevice may transmit SPS traffic on radio resources identified in the SPSgrant considering the SPS traffic associated with the traffic indexvalue. The DCI grant may include one or more parameters identifying thetraffic associated with the grant. Example embodiment may be employedwith one or more SPS C-RNTI are configured.

In an example, eNB may configure a V2X UL SPS RNTI for the UE. The V2XUL SPS RNTI may be different from the legacy SPS C-RNTI. In an example,a DCI format 0 scrambled with V2X UL SPS RNTI may be used to activateand/or update the V2X SPS for the UE.

In an example, multiple SPS configurations can be active at the sametime. In an example, one or more indicators in the DCI activating theSPS (e.g., DCI format 0) may be used to differentiate SPSconfigurations. In an example, the one or more indicator may be SPSindex and/or one or more indicator mapped to the SPS index.

In an example, a SPS configuration index may be signaled to the UE whenthe eNB activates and/or reactivates and/or updates the SPS for the UE.In an example, the eNB may use the Cyclic shift DM RS field (3 bits) inDCI 0 to indicate to the UL SPS configuration index to the UE. In anexample, another field in DCI format 0 (e.g., the TPC command field (2bits)) in DCI 0 may be considered to indicate UL SPS configurationindex.

In an example, the eNB may activate a single SPS configuration with aDCI and the UL SPS DCI may contain a single SPS configuration index. Inan example, the eNB may transmit multiple DCIs for activation ofmultiple SPS configurations. In an example, the eNB may transmit as manyDCIs as the SPS configurations that the eNB activates for a UE.

In an example, activation of one SPS configuration may release theprevious allocation for the same SPS configuration.

In an example, the eNB may explicitly release a SPS configuration for aUE. In an example, the eNB may explicitly release the SPS by sending aDCI (e.g., DCI 0) and the UE may validate the DCI as an indication forrelease by comparing one or more fields of the DCI with pre-configuredvalues. In an example, the UE may release the SPS without explicitindication of the eNB. Both explicit release and implicit releasemechanisms for SPS over Uu may be supported.

In an example, the UE may explicitly signal to the eNB (e.g., using MACCE and/or with one or more RRC messages) to indicate to the eNB when theUE desires to activate and/or update and/or release a SPS configuration.In an example, when the UE indicates to the eNB that it desires toactivate a SPS configuration, the UE may include a desirable time offsetin its indication to the eNB. In an example, the desirable time offsetmay be relative to system frame number 0 (SFN0).

In an example, when the UE desires to change the period of a SPSconfiguration, the UE may signal this to the eNB. In an example, thesignaling may be in form of MAC CE. In an example, the signaling may bein form of RRC signaling.

In an example, in the event of a resource conflict between SPSconfigurations (e.g., two or more SPS grants from two or more SPSconfigurations in a subframe), only one transmission may occur. In anexample, a mechanism and/or rule may be used for resolving resourceconflicts between SPS configurations.

In an example, the eNB may configure an SL SPS RNTI different from SLdynamic scheduling RNTI for a UE. In an example, two fields may beincluded in the DCI scheduling the SL SPS. In an example, a SL SPSconfiguration index may be included in the DCI scheduling SL SPS. In anexample, the SL SPS configuration index may be 3 bits. In an example anActivation/release indication may be included in the DCI scheduling theSL SPS. In an example, the Activation/release indication field may be 1bit.

In an example, a SL SPS DCI may contain a single SPS configurationindex.

In an example, if the number of information bits in SL SPS DCI formatmapped onto a given search space is less than the payload size of DCIformat 0 mapped onto the same search space, zeros may be appended to SLSPS DCI format until the payload size equals that of DCI format 0including any padding bits appended to DCI format 0.

In an example, the size of SL SPS DCI format may be larger than the sizeof DCI format 0 on the same search space. In an example, a UE may use anacknowledgement feedback mechanism after the reception of a DCIindicating SL SPS activation and/or release. In an example, a countermay be used by the MAC and the SPS may be released if there is no MACPDU for a configured number of consecutive SPS occasions without data.In an example, when a SPS configuration is activated for an SPS process,previously configured SPS process may be released.

In an example, a UE may identify a SPS process associated to a DCI basedon the contents of the DCI. In an example, there may be one-to-onemapping between SPS configuration index and SPS process. In an example,there may be semi-static (e.g., configured by higher layer) associationbetween SPS configuration index and SPS process. Multiple SPSconfigurations can be associated to a SPS process. In an example, theremay be dynamic indication (e.g., explicitly and/or implicitly) of SPSprocess associated to a SPS DCI.

In an example, a UE configured with SPS may transmit assistanceinformation to the eNB to activate and/or release and/or update a SPSconfiguration. In an example, the UE assistance may be signaled to theeNB with MAC CE and/or one or more RRC messages.

In an example, the UE assistance information reporting may be triggeredbased on UE implementation. In an example, some rules may be used tolimit the amount of UE assistance reporting from UE. In an example, theUE assistance report may not be sent if the offset to the next SPSoccasion is not greater than a threshold. In an example, the thresholdmay be configured. In an example, a prohibit timer may be used. In anexample, the eNB may control the UE assistance reporting. In an example,the trigger to transmit the UE assistance may be cancelled based on somerule. In an example, the trigger to transmit the UE assistance may becancelled if the eNB activates and/or reactivates a SPS configurationthat matches the UE requirement (e.g., with a periodicity and timingoffset that matches the UE data).

In an example, the UE assistance information may include the periodicityand timing offset. In an example, the UE may send the preferred SPSinterval in the assistance information if the periodicity of packetgeneration changes. In an example, the preferred SPS interval in the UEassistance information may be expected packet periodicity. In anexample, the preferred SPS interval in the UE assistance information maybe the interval between the last two generated packets. In an example,the preferred SPS interval in the UE assistance information may beaverage inter-packet generation time for a last period of time. In anexample, the last period of time may be configured for the UE. In anexample, the last period of time may be RRC configured for the UE. In anexample, the UE may estimate the periodicity and timing offset based onUE implementation.

In an example, the UE assistance triggers may be left to UEimplementation. In an example, the network may configure the UEassistance information for the UE. In an example, explicit SPS resourcerelease by eNB may be based on UE's transmission or indications. In anexample, the UE assistant information may include a set of preferredexpected SPS interval, timing offset with respect subframe0 of the SFN0.In an example, SPS periodicity values may be 50 ms, 100 ms, 200 ms, 300ms, 400 ms, 500 ms, 600 ms, 700 ms, 800 ms, 900 ms and 1000 ms UL and/orSPS.

In an example, the UE assistance information may be per logical channel.In an example, the UE assistance information may be reported if changeis estimated in periodicity of packet arrival. In an example, the UEassistance information may be reported if change is estimated in offsetof packet arrival. In an example, the UE assistance information may beconfigured by the eNB. In an example, the UE assistance information maybe reported in case SPS configured for the UE and/or in case SPS is notconfigured for the UE. In an example, the UE assistance information mayinclude the existing or a suggested SPS configuration. In an example,the UE assistance information may include the index of SPSconfiguration.

In an example, up to 8 SPS configurations may be configured per UE. Inan example, 3 bits may be used in the scheduling DCI that may correspondto the 8 SPS configurations. In an example, the configured SPSs may besimultaneously active. In an example, there may be an associationbetween a SPS configuration and logical channel ID (LCID) and/or ProSePer-Packet Priority (PPPP). In an example, the association in UL SPS maybe based on LCID. In an example, the association in SL SPS may be basedon PPPP. In an example, one traffic type (e.g., one LCID and/or one PPPPmay be associated to multiple SPS configurations.

In an example, the eNB may configure the UE with a sidelink SPS releasemechanism. In an example, after a configurable number of consecutivesidelink SPS occasions are not used by the UE, the UE may notify thenetwork and may consider the specific sidelink SPS released. In anexample, the eNB may configure a valid duration for an SPS activated. Inan example, the valid duration may be configured by RRC. In an example,when the time elapsed exceeds the valid duration since the activationfor a specific SPS, the UE and eNB may implicitly release the SPS. In anexample, if a sidelink SPS release mechanism is not configured by theeNB, it may be up to UE implementation to determine when a sidelinktraffic is terminated and report this information to the eNB. In anexample, the UE may report the information using MAC CE. In an example,the UE may report this information using PUCCH and/or a UCI.

In an example, the SPS configurations may be provided by the eNB to UEsin RRC signaling. In an example, the SPS configuration may compriseSidelink SPS scheduling interval (e.g., the specific SPS periodicity forthe SPS configuration), the index of the SPS configuration (e.g., theindex that may be used by PDCCH in DCI to (re)activate/release aconfigured SPS configuration. The SPS index may also be used in the UEassistance information), the LCID associated to the SPS configuration,the PPPP associated to the SPS configuration, the number of sidelinkempty transmissions before release, the carrier in which this SPSconfiguration applies (e.g., in case of multi-carrier sidelinktransmissions, it may indicate the carrier in which a specific SPSconfiguration applies), the destination L2 ID associated to the SPSconfiguration, the valid duration associated to the SPS configuration,etc.

In an example, the UE assistance information may be reported both incase SPS is configured or not. In an example, the report of the UEassistance information may be configured by the eNB only for certainlogical channels/PPPP. In an example, the UE may report theperiodicity/offset changes of the traffics associated to those logicalchannels/PPPP configured by the eNB. In an example, the UE assistanceinformation, if configured, may be reported by the UE for any logicalchannel/PPPP. In an example, the UE assistance information may bereported by the UE for any logical channel identified by a pair of LCIDand Destination L2 ID. In an example, the UE assistance information maybe delivered in a MAC CE and/or in RRC. In an example, the UE assistanceinformation may use the existing RRC message UEAssistanceInformationwith some new fields introduced.

In an example, the estimated periodicity of packet arrivals, theestimated offset with respect to subframe0 of the SFN0, and the SPSindex of the SPS configuration (e.g., if SPS is configured by the eNB)may be included in the UE assistance information. In an example, the UEmay indicate in the UE assistance message, the LCID to which the contentof the UE Assistance Information is associated. In an example, the UEmay indicate in the UE assistance message, the PPPP to which the contentof the UE Assistance Information is associated. In an example, the UEmay indicate, in the UE assistance message, the estimated packet size ofnext transmission. In an example, the UE may indicate, in the UEassistance message, the Destination L2 ID for the associated logicalchannel.

In an example, the AS-Context information element may be used totransfer local E-UTRAN context required by the target eNB. In anexample, idc-Indication may include information used for handling theIDC problems. In an example, reestablishmentInfo may include informationneeded for the RRC connection re-establishment. In an example, the HOfield may be mandatory present in case of handover within E-UTRA. In anexample, HO2 field may be optionally present in case of handover withinE-UTRA.

In an example, the UEAssistanceInformation message may be used for theindication of UE assistance information to the eNB. In an example, thesignalling radio bearer may be SRB1. In an example, the RLC-SAP mode maybe AM. In an example, the corresponding logical channel may be DCCH. Inan example, direction of this message may be from UE to the E-UTRAN.

In an example, the value lowPowerConsumption of powerPrefIndication mayindicate the UE prefers a configuration that is primarily optimised forpower saving. In an example, the value of powerPrefIndication may be setto normal.

In an example, for X2 based handover, the handover source eNB mayinitiate the procedure by sending the HANDOVER REQUEST message to thetarget eNB. When the source eNB sends the HANDOVER REQUEST message, itmay start the timer TRELOCprep.

The allocation of resources according to the values of the Allocationand Retention Priority IE included in the E-RAB Level QoS Parameters IEmay follow the principles of an E-RAB Setup procedure. The source eNBmay include in the GUMMEI IE and/or GUMMEI corresponding to the sourceMME node. If at least one of the requested non-GBR E-RABs is admitted tothe cell indicated by the Target Cell ID IE, the target eNB may reservenecessary resources, and/or send the HANDOVER REQUEST ACKNOWLEDGEmessage back to the source eNB. The target eNB may include the E-RABsfor which resources have been prepared at the target cell in the E-RABsAdmitted List IE. The target eNB may include the E-RABs that have notbeen admitted in the E-RABs Not Admitted List IE with an appropriatecause value.

At reception of the HANDOVER REQUEST message the target eNB may preparethe configuration of the AS security relation between the UE and thetarget eNB by using the information in the UE Security Capabilities IEand the AS Security Information IE in the UE Context Information IE.

In an example, for E-RAB for which the source eNB proposes to doforwarding of downlink data, the source eNB may include the DLForwarding IE within the E-RABs To be Setup Item IE of the HANDOVERREQUEST message. For E-RAB that it has decided to admit, the target eNBmay include the DL GTP Tunnel Endpoint IE within the E-RABs AdmittedItem IE of the HANDOVER REQUEST ACKNOWLEDGE message to indicate that itaccepts the proposed forwarding of downlink data for this bearer. ThisGTP tunnel endpoint may be different from the corresponding GTP TEID IEin the E-RAB To Be Switched in Downlink List IE of the PATH SWITCHREQUEST message depending on implementation choice.

For bearer in the E-RABs Admitted List IE, the target eNB may includethe UL GTP Tunnel Endpoint IE to indicate that it requests dataforwarding of uplink packets to be performed for that bearer.

In an example, upon reception of the HANDOVER REQUEST ACKNOWLEDGEmessage the source eNB may stop the timer TRELOCprep, start the timerTX2RELOCoverall and terminate the Handover Preparation procedure. Thesource eNB may be defined to have a Prepared Handover for that X2UE-associated signalling.

In an example, if the Trace Activation IE is included in the HANDOVERREQUEST message, the target eNB may, if supported, initiate therequested trace function as described in TS 32.422 [6]. In particular,the target eNB may, if supported: if the Trace Activation IE does notinclude the MDT Configuration IE, initiate the requested trace session;if the Trace Activation IE includes the MDT Activation IE, within theMDT Configuration IE, set to “Immediate MDT and Trace” initiate therequested trace session and MDT session; if the Trace Activation IEincludes the MDT Activation IE, within the MDT Configuration IE, set to“Immediate MDT Only” initiate the requested MDT session and the targeteNB may ignore Interfaces To Trace IE, and Trace Depth IE; if the TraceActivation IE includes the MDT Location Information IE, within the MDTConfiguration IE, store this information and take it into account in therequested MDT session; or if the Trace Activation IE includes theSignalling based MDT PLMN List IE, within the MDT Configuration IE, theeNB may use it to propagate the MDT Configuration.

In an example, if the Management Based MDT Allowed IE only or theManagement Based MDT Allowed IE and the Management Based MDT PLMN ListIE is contained in the HANDOVER REQUEST message, the target eNB may, ifsupported, store the received information in the UE context, and usethis information to allow subsequent selection of the UE for managementbased MDT. In an example, if the Masked IMEISV IE is contained in theHANDOVER REQUEST message the target eNB may, if supported, use it todetermine the characteristics of the UE for subsequent handling.

In an example, the source eNB may, if supported and available in the UEcontext, include the Management Based MDT Allowed IE and the ManagementBased MDT PLMN List IE in the HANDOVER REQUEST message, except if thesource eNB selects a serving PLMN in the target eNB which is notincluded in the Management Based MDT PLMN List. If the Management BasedMDT PLMN List IE is not present, the source eNB may, if supported,include the Management Based MDT Allowed IE, if this information isavailable in the UE context, in the HANDOVER REQUEST message, except ifthe source eNB selects a serving PLMN in the target eNB different fromthe serving PLMN in the source eNB.

In an example, if the Handover Restriction List IE is contained in theHANDOVER REQUEST message, the target eNB may store the informationreceived in the Handover Restriction List IE in the UE context, use thisinformation to determine a target for the UE during subsequent mobilityaction for which the eNB provides information about the target of themobility action towards the UE, except when one of the E-RABs has aparticular ARP value in which case the information may not apply, and/oruse this information to select a proper SCG during dual connectivityoperation. If the Handover Restriction List IE is not contained in theHANDOVER REQUEST message, the target eNB may consider that no roamingand no access restriction apply to the UE.

In an example, if the Location Reporting Information IE is included inthe HANDOVER REQUEST message, the target eNB may initiate the requestedlocation reporting functionality. If the SRVCC Operation Possible IE isincluded in the HANDOVER REQUEST message, the target eNB may store thecontent of such IE in the UE context and use it. If the UE SecurityCapabilities IE included in the HANDOVER REQUEST message only containsthe EIAO algorithm and if this EIAO algorithm is defined in theconfigured list of allowed integrity protection algorithms in the eNB,the eNB may take it into use and ignore the keys received in the ASSecurity Information IE.

In an example, the HANDOVER REQUEST message may contain the SubscriberProfile ID for RAT/Frequency priority IE, if available. If theSubscriber Profile ID for RAT/Frequency priority IE is contained in theHANDOVER REQUEST message, the target eNB may store this information andthe target eNB may use the information. Upon reception of UE HistoryInformation IE in the HANDOVER REQUEST message, the target eNB maycollect the information defined as mandatory in the UE HistoryInformation IE and may, if supported, collect the information defined asoptional in the UE History Information IE, for as long as the UE staysin one of its cells, and store the collected information to be used forfuture handover preparations. Upon reception of the UE HistoryInformation from the UE IE in the HANDOVER REQUEST message, the targeteNB may, if supported, store the collected information to be used forfuture handover preparations. If the Mobility Information IE is providedin the HANDOVER REQUEST message, the target eNB may, if supported, storethis information and use it. The target eNB may, if supported, store theC-RNTI of the source cell received in the HANDOVER REQUEST message.

In an example, if the Expected UE Behavior IE is provided in theHANDOVER REQUEST message, the target eNB may, if supported, store thisinformation and may use it to determine the RRC connection time. If theProSe Authorized IE is contained in the HANDOVER REQUEST message and itcontains one or more IEs set to “authorized”, the eNB may, if supported,consider that the UE is authorized for the relevant ProSe service(s). Ifthe V2X Services Authorized IE is contained in the HANDOVER REQUESTmessage and it contains one IE set to “authorized”, the eNB may, ifsupported, consider that the UE is authorized for the relevantservice(s). If the UE Context Reference at the SeNB IE is contained inthe HANDOVER REQUEST message the target eNB may use it. In this case,the source eNB may expect the target eNB to include the UE Context KeptIndicator IE set to “True” in the HANDOVER REQUEST ACKNOWLEDGE message,which may use this information. If the Bearer Type IE is included in theHANDOVER REQUEST message and is set to “non IP”, the target eNB may notperform header compression for the concerned E-RAB.

In an example, for S1 based handover, the source eNB may initiate thehandover preparation by sending the HANDOVER REQUIRED message to theserving MME. When the source eNB sends the HANDOVER REQUIRED message, itmay start the timer TS1RELOCprep. The source eNB may indicate theappropriate cause value for the handover in the Cause IE. The source eNBmay include the Source to Target Transparent Container IE in theHANDOVER REQUIRED message.

In an example, in case of intra-system handover, the information in theSource to Target Transparent Container IE may be encoded according tothe definition of the Source eNB to Target eNB Transparent Container IE.In case of handover to UTRAN, the information in the Source to TargetTransparent Container IE may be encoded according to the Source RNC toTarget RNC Transparent Container IE definition and/or the source eNB mayinclude the UE History Information IE in the Source RNC to Target RNCTransparent Container IE. If the handover is to GERAN A/Gb mode, theinformation in the Source to Target Transparent Container IE may beencoded according to the definition of the Source BSS to Target BSSTransparent Container IE. When the preparation, including thereservation of resources at the target side is ready, the MME mayrespond with the HANDOVER COMMAND message to the source eNB.

In an example, if the Target to Source Transparent Container IE has beenreceived by the MME from the handover target, the transparent containermay be included in the HANDOVER COMMAND message. Upon reception of theHANDOVER COMMAND message the source eNB may stop the timer TS1RELOCprepand start the timer TS1RELOCOverall.

In an example, in case of intra-system handover, the information in theTarget to Source Transparent Container IE may be encoded according tothe definition of the Target eNB to Source eNB Transparent Container IE.In case of inter-system handover to UTRAN, the information in the Targetto Source Transparent Container IE may be encoded according to theTarget RNC to Source RNC Transparent Container IE. In case ofinter-system handover to GERAN A/Gb mode, the information in the Targetto Source Transparent Container IE may be encoded according to theTarget BSS to Source BSS Transparent Container IE definition. In anexample, if there are any E-RABs that could not be admitted in thetarget, they may be indicated in the E-RABs to Release List IE.

In an example, if the DL forwarding IE is included within the Source eNBto Target eNB Transparent Container IE of the HANDOVER REQUIRED messageand/or it is set to “DL forwarding proposed”, it may indicate that thesource eNB proposes forwarding of downlink data. In an example, if theMME receives the Direct Forwarding Path Availability IE in the HANDOVERREQUIRED message indicating that a direct data path is available, it mayhandle it.

In an example, if the CSG Id IE and no Cell Access Mode IE are receivedin the HANDOVER REQUIRED message, the MME may perform the access controlaccording to the CSG Subscription Data of that UE and, if the accesscontrol is successful or if at least one of the E-RABs has a particularARP value, it may continue the handover and propagate the CSG Id IE tothe target side. If the access control is unsuccessful but at least oneof the E-RABs has a particular ARP value, the MME may provide the CSGMembership Status IE set to “non-member” to the target side. In anexample, if the CSG Id IE and the Cell Access Mode IE set to “hybrid”are received in the HANDOVER REQUIRED message, the MME may provide themembership status of the UE and the CSG Id to the target side.

In an example, the source eNB may include the SRVCC HO Indication IE inthe HANDOVER REQUIRED message if the SRVCC operation is needed. Thesource eNB may indicate to the MME in the SRVCC HO Indication IE if thehandover may be prepared for PS and CS domain or only for CS domain. TheSRVCC HO Indication IE is set according to the target cell capabilityand UE capability. In case the target system is GERAN without DTMsupport or the UE is without DTM support, the source eNB may indicate“CS only” in the SRVCC HO Indication IE and “PS service not available”in PS Service Not Available IE. In case the target system is eitherGERAN with DTM but without DTM HO support and the UE is supporting DTMor the target system is UTRAN without PS HO support, the source eNB mayindicate “CS only” in the SRVCC HO Indication IE. Otherwise, the sourceeNB may indicate “PS and CS” in the SRVCC HO Indication IE.

In an example, in case of inter-system handover from E-UTRAN, the sourceeNB may indicate in the Target ID IE, in case the target system isUTRAN, the Target RNC-ID of the RNC (including the Routing Area Codeonly in case the UTRAN PS domain is involved), in case the target systemis GERAN the Cell Global Identity (including the Routing Area Code onlyin case the GERAN PS domain is involved) of the cell in the targetsystem.

In an example, in case of inter-system handover from E-UTRAN to UTRAN,the source eNB may, if supported, include the HO Cause Value IE in theUE History Information IE of the HANDOVER REQUIRED message. In anexample, in case the SRVCC operation is performed and the SRVCC HOIndication IE indicates that handover may be prepared only for CSdomain, and if the target system is GERAN, the source eNB: may encodethe information in the Source to Target Transparent Container IE withinthe HANDOVER REQUIRED message, according to the definition of the OldBSS to New BSS information IE; and/or may not include the Source toTarget Transparent Container Secondary IE in the HANDOVER REQUIREDmessage. If the target system is UTRAN, the source eNB: may encode theinformation in the Source to Target Transparent Container IE within theHANDOVER REQUIRED message according to the definition of the Source RNCto Target RNC Transparent Container IE; may include the UE HistoryInformation IE in the Source RNC to Target RNC Transparent Container IE;and/or may not include the Source to Target Transparent ContainerSecondary IE in the HANDOVER REQUIRED message.

In an example, in case the SRVCC operation is performed, the SRVCC HOIndication IE in the HANDOVER REQUIRED message may indicate thathandover may be prepared for PS and CS domain, and if the target systemis GERAN with DTM HO support, the source eNB: may encode the informationin the Source to Target Transparent Container IE within the HANDOVERREQUIRED message according to the definition of the Source BSS to TargetBSS Transparent Container IE; and/or may include the Source to TargetTransparent Container Secondary IE in the HANDOVER REQUIRED message andencode information in it according to the definition of the Old BSS toNew BSS information IE. If the target system is UTRAN, the source eNB:may encode the information in the Source to Target Transparent ContainerIE within the HANDOVER REQUIRED message according to the definition ofthe Source RNC to Target RNC Transparent Container IE; may include theUE History Information IE in the Source RNC to Target RNC TransparentContainer IE; and/or may not include the Source to Target TransparentContainer Secondary IE in the HANDOVER REQUIRED message.

In an example, if the HANDOVER COMMAND message contains the DL GTP-TEIDIE and the DL Transport Layer Address IE for a given bearer in theE-RABs Subject to Forwarding List IE, the source eNB may consider thatthe forwarding of downlink data for this given bearer is possible. Ifthe HANDOVER COMMAND message contains the UL GTP-TEID IE and the ULTransport Layer Address IE for a given bearer in the E-RABs Subject toForwarding List IE, it may mean the target eNB has requested theforwarding of uplink data for this given bearer.

In an example, if, after a HANDOVER REQUIRED message is sent and beforethe Handover Preparation procedure is terminated, the source eNBreceives an MME initiated E-RAB Management procedure on the same UEassociated signalling connection, the source eNB may either: cancel theHandover Preparation procedure by executing the Handover Cancelprocedure with an appropriate cause value. After successful completionof the Handover Cancel procedure, the source eNB may continue the MMEinitiated E-RAB Management procedure; or terminate the MME initiatedE-RAB Management procedure by sending the appropriate response messagewith an appropriate cause value, e.g., “S1 intra system HandoverTriggered”, “S1 inter system Handover Triggered” to the MME and thesource eNB may continue with the handover procedure.

In an example, for S1 based handover, the MME may initiate the procedureby sending the HANDOVER REQUEST message to the target eNB. The HANDOVERREQUEST message may contain the Handover Restriction List IE, which maycontain roaming or access restrictions. In an example, if the HandoverRestriction List IE is contained in the HANDOVER REQUEST message, thetarget eNB may store this information in the UE context. Thisinformation may not be considered whenever one of the handed over E-RABshas a particular ARP value.

In an example, the target eNB may use the information in HandoverRestriction List IE if present in the HANDOVER REQUEST message todetermine a target for subsequent mobility action for which the eNBprovides information about the target of the mobility action towards theUE, and/or to select a proper SCG during dual connectivity operation. Inan example, if the Handover Restriction List IE is not contained in theHANDOVER REQUEST message, the target eNB may consider that no roamingand no access restriction apply to the UE. In an example, upon receptionof the HANDOVER REQUEST message, the eNB may store the received UESecurity Capabilities IE in the UE context and use it to prepare theconfiguration of the AS security relation with the UE.

In an example, if the SRVCC Operation Possible IE is included in theHANDOVER REQUEST message, the target eNB may store the content of thereceived SRVCC Operation Possible IE in the UE context and, ifsupported, use it. In an example, upon reception of the HANDOVER REQUESTmessage, the eNB may store the received Security Context IE in the UEcontext and the eNB may use it to derive the security configuration. Inan example, if the Trace Activation IE is included in the HANDOVERREQUEST message, the target eNB may, if supported, initiate therequested trace function. In example embodiments, the eNB may: if theTrace Activation IE does not include the MDT Configuration IE, initiatethe requested trace session; if the Trace Activation IE includes the MDTActivation IE, within the MDT Configuration IE, set to “Immediate MDTand Trace”, initiate the requested trace session and MDT session; if theTrace Activation IE includes the MDT Activation IE, within the MDTConfiguration IE, set to “Immediate MDT Only”, “Logged MDT only” or“Logged MBSFN MDT”, initiate the requested MDT session and/or the targeteNB may ignore Interfaces To Trace IE, and/or Trace Depth IE; if theTrace Activation IE includes the MDT Location Information IE, within theMDT Configuration IE, store this information and take it into account inthe requested MDT session; if the Trace Activation IE includes theSignalling based MDT PLMN List IE, within the MDT Configuration IE, theeNB may use it to propagate the MDT Configuration; if the TraceActivation IE includes the MBSFN-ResultToLog IE, within the MDTConfiguration IE, take it into account for MDT

Configuration; if the Trace Activation IE includes the MBSFN-Areald IEin the MBSFN-ResultToLog IE, within the MDT Configuration IE, take itinto account for MDT Configuration; or If the CSG Id IE is received inthe HANDOVER REQUEST message, the eNB may compare the received valuewith the CSG Id broadcast by the target cell.

In an example, if the CSG Membership Status IE is received in theHANDOVER REQUEST message and the CSG Membership Status is set to“member”, the eNB may provide the QoS to the UE as for member providedthat the CSG Id received in the HANDOVER REQUEST messages corresponds tothe CSG Id broadcast by the target cell. In an example, if the CSGMembership Status IE and the CSG Id IE are received in the HANDOVERREQUEST message and the CSG Id does not correspond to the CSG Idbroadcast by the target cell, the eNB may provide the QoS to the UE asfor a non-member and may send back in the HANDOVER REQUEST ACKNOWLEDGEmessage the actual CSG Id broadcast by the target cell. In an example,if the target cell is CSG cell or hybrid cell, the target eNB mayinclude the CSG ID IE in the HANDOVER REQUEST ACKNOWLEDGE message.

In an example, if the target eNB receives the CSG Id IE and the CSGMembership Status IE is set to “non member” in the HANDOVER REQUESTmessage and the target cell is a closed cell and at least one of theE-RABs has a particular ARP value, the eNB may send back the HANDOVERREQUEST ACKNOWLEDGE message to the MME accepting those E-RABs andfailing the other E-RABs. In an example, if the Subscriber Profile IDfor RAT/Frequency priority IE is contained in the Source eNB to TargeteNB Transparent Container IE, the target eNB may store the content ofthe received Subscriber Profile ID for RAT/Frequency priority IE in theUE context and use it.

In an example, upon reception of the UE History Information IE, whichmay be included within the Source eNB to Target eNB TransparentContainer IE in the HANDOVER REQUEST message, the target eNB may collectthe information defined as mandatory in the UE History Information IE,and/or may, if supported, collect the information defined as optional inthe UE History Information IE, for as long as the UE stays in one of itscells, and store the collected information to be used for futurehandover preparations. In an example, upon reception of the UE HistoryInformation from the UE IE, which may be included within the Source eNBto Target eNB Transparent Container IE in the HANDOVER REQUEST message,the target eNB may, if supported, store the collected information, to beused for future handover preparations.

In an example, if the Mobility Information IE is included within theSource eNB to Target eNB Transparent Container IE in the HANDOVERREQUEST message, the target eNB may, if supported, store thisinformation and use it. In an example, if the Expected UE Behaviour IEis included in the HANDOVER REQUEST message, the eNB may, if supported,store this information and may use it to determine the RRC connectiontime. In an example, if the Bearer Type IE is included in the HANDOVERREQUEST message and is set to “non IP”, the eNB may not perform headercompression for the concerned E-RAB.

In an example, after all necessary resources for the admitted E-RABshave been allocated, the target eNB may generate the HANDOVER REQUESTACKNOWLEDGE message. The target eNB may include in the E-RABs AdmittedList IE the E-RABs for which resources have been prepared at the targetcell. The E-RABs that have not been admitted in the target cell, if any,may be included in the E-RABs Failed to Setup List IE. In an example, ifthe HANDOVER REQUEST message contains the Data Forwarding Not PossibleIE associated with a given E-RAB within the E-RABs To Be Setup List IEset to “Data forwarding not possible”, the target eNB may decide not toinclude the DL Transport Layer Address IE and the DL GTP-TEID IE and forintra LTE handover the UL Transport Layer Address IE and the UL GTP-TEIDIE within the E-RABs Admitted List IE of the HANDOVER REQUESTACKNOWLEDGE message for that E-RAB.

In an example, for a bearer that target eNB has decided to admit and forwhich DL forwarding IE is set to “DL forwarding proposed”, the targeteNB may include the DL GTP-TEID IE and the DL Transport Layer Address IEwithin the E-RABs Admitted List IE of the HANDOVER REQUEST ACKNOWLEDGEmessage indicating that it accepts the proposed forwarding of downlinkdata for this bearer. In an example, if the HANDOVER REQUEST ACKNOWLEDGEmessage contains the UL GTP-TEID IE and the UL Transport Layer AddressIE for a given bearer in the E-RABs Admitted List IE, it may mean thetarget eNB has requested the forwarding of uplink data for this givenbearer. In an example, if the Request Type IE is included in theHANDOVER REQUEST message, the target eNB may perform the requestedlocation reporting functionality for the UE.

In an example, if the UE Security Capabilities IE included in theHANDOVER REQUEST message only contains the EIAO algorithm and/or if thisEIAO algorithm is defined in the configured list of allowed integrityprotection algorithms in the eNB, the eNB may take it into use andignore the keys received in the Security Context IE. In an example, theGUMMEI IE may only be contained in the HANDOVER REQUEST message. If theGUMMEI IE is present, the target eNB may store this information in theUE context and use it for subsequent X2 handovers. In an example, theMME UE S1AP ID 2 IE may only be contained in the HANDOVER REQUESTmessage. In an example, if the MME UE S1AP ID 2 IE is present, thetarget eNB may store this information in the UE context and use it forsubsequent X2 handovers.

In an example, if the Management Based MDT Allowed IE only or theManagement Based MDT Allowed IE and the Management Based MDT PLMN ListIE is contained in the HANDOVER REQUEST message, the target eNB may, ifsupported, store the received information in the UE context, and usethis information to allow subsequent selections of the UE for managementbased MDT. In an example, if the Masked IMEISV IE is contained in theHANDOVER REQUEST message the target eNB may, if supported, use it todetermine the characteristics of the UE for subsequent handling. In anexample, if the HANDOVER REQUEST contains a Target Cell ID IE, as partof the Source eNB to Target eNB Transparent Container IE, for a cellwhich is no longer active, the eNB may respond with an HANDOVER REQUESTACKNOWLEDGE in case the PCI of the deactivated cell is in use by anotheractive cell.

In an example, if the ProSe Authorized IE is contained in the HANDOVERREQUEST message and it contains one or more IEs set to “authorized”, theeNB may, if supported, consider that the UE is authorized for therelevant ProSe service(s). In an example, if the UE User Plane CIoTSupport Indicator IE is included in the HANDOVER REQUEST message and isset to “supported”, the eNB may, if supported, consider that User PlaneCIoT EPS Optimisation is supported for the UE. In an example, if theCE-mode-B Support Indicator IE is included in the HANDOVER REQUESTACKNOWLEDGE message and set to “supported”, the MME may, if supported,use the extended NAS timer settings for the UE. In an example, if theV2X Services Authorized IE is contained in the HANDOVER REQUEST messageand it contains one IE set to “authorized”, the eNB may, if supported,consider that the UE is authorized for the relevant service(s).

In an example embodiment, in FIG. 14 , a target base station of ahandover for a wireless device may receive, from a source base stationof the handover, traffic pattern parameters for SPS traffic of thewireless device via a handover request message during the handoverprocedure. The traffic pattern parameters may comprise a trafficperiodicity, a timing offset, and a message size of an SPS traffic. Thetarget base station may determine an activation timing for SPS radioresource based on the timing offset, which may indicate an offset (e.g.offset time value) from subframe 0 of SFN 0. After the wireless deviceconnects to the target base station by performing a random access (RA)procedure, the target base station may transmit an SPS activationcontrol command (via DCI, PDCCH command) to the wireless device based onthe determination of the activation timing. The target base station maytransmit the SPS activation control command in a subframe correspondingto the activation timing. The wireless device may start transmittingpackets of the SPS traffic after “k” time duration from the SPSactivation control command

In an example, the target base station may further determine an SPSperiodicity (e.g. SPS resource periodicity) based on the trafficperiodicity of the traffic pattern parameters received via the handoverrequest message. The SPS periodicity may be sent to the wireless devicevia a handover request acknowledge message (e.g. X2 message, S1 message)and a handover command message (e.g. RRC message). After receiving theSPS activation control command and transmitting first packets of the SPStraffic after “k” time duration from the SPS activation control command,the wireless device may transmit further packets of the SPS traffic viaSPS resources coming after the SPS periodicity from the first packettransmission. The wireless device may transmit packets of the SPStraffic to the base station periodically with a periodic duration of theSPS periodicity.

An issue with respect to SPS configuration is how eNB configures SPS forthe UE and how SPS configuration may be maintained or updated during ahandover. In an example embodiment, some UEs may support enhanced SPSconfiguration, e.g. multiple SPS configuration/activation, SPS onsidelink, SPS configuration/activation on SCell, and/or SPS UEassistance information transmission. SPS configuration may be employedfor V2X communications. In an example, V2X configurations may compriseSPS configuration parameters, for example, SPS configuration parameterson PCell and/or SCell. In an example embodiment, SPS may be employed fortransmission of V2X traffic. Example V2X messages are shown below.

In an example, cooperative awareness messages (CAM) message generationmay be dynamic in terms of size, periodicity and timing. Such changesmay result in misalignment between SPS timing and CAM timing. There maybe some regularity in size and periodicity between different triggers.SPS may be beneficial for some cases and SPS may be configured. UEassistance may be needed to trigger and/or employ SPS.

In an example, CAM may comprise status information (e.g. time, position,motion state, activated system, and/or the like) and/or attributeinformation (e.g. data about dimension, vehicle type and/or role in theroad traffic, and/or the like). Decentralized environmental notificationmessage (DENM) may comprise information related to a variety of events.Basic safety message (BSM) may comprise some of basic vehicle stateinformation (e.g. message identifier, vehicle identifier, vehiclelatitude/longitude, speed, acceleration status, and/or the like) and/ortwo option data frames (e.g. vehicle safety extension and/or vehiclestatus).

In an example, the eNB may configure multiple SPS configurations for agiven UE. In an example, SPS-configuration-specific MCS (if MCS is partof the SPS-configuration) and/or SPS-configuration-specific periodicitymay be configured. Some SPS parameters may differ across theSPS-configurations. The eNB may dynamically trigger/release thedifferent SPS-configurations by use of (E)PDCCH. The UE may indicate tothe eNB that it does not intend to transmit data before a transmissionassociated to an SPS configuration. SPS configuration in thespecification refers to V2X and/or enhanced SPS configuration. LegacyLTE devices may support SPS configuration. In the specifications, SPSconfiguration refers to, for example, multiple SPSconfiguration/activation, SPS on sidelink, SPS configuration/activationon SCell, and/or SPS UE assistance information transmission, and/orother enhanced SPS features. These configurations may not be necessarilyemployed for V2X and may be applicable to other applications. In anexample, SPS feature may be referred to SPS or enhanced SPS feature.

In an example, a UE may be configured with a first SPS configurationwith a serving eNB. In an example, a first SPS configuration for a UEmay be decided by a serving eNB based on UE assistance informationreceived from the UE. A target eNB may maintain the same SPSconfiguration, or may update the UE SPS configuration. The target eNBmay have a different cell configuration and may require a different SPSconfiguration. In another example embodiment, the target eNB may employcells with the same frequencies as the serving cell and may requiremaintaining the same SPS configuration. The target eNB may configure SPSconfiguration after the handover is completed or may configure SPSconfiguration during the handover process. There is a need fordeveloping a signalling flow, UE processes, and eNB processes to addressSPS configuration, and SPS configuration parameter handling, and SPSactivation during the handover to reduce the handover overhead anddelay, and increase handover efficiency. Furthermore, there is a need todevelop handover signalling and handover message parameters to addressSPS configuration and/or activation during a handover process.

In an example, according to some of the various aspects of embodiments,in RRC_CONNECTED mode, the network may control UE mobility, for example,the network may decide when the UE connects to which E-UTRA cell(s) orinter-RAT cell. For network controlled mobility in RRC_CONNECTED, thePCell may be changed using an RRC Connection Reconfiguration messageincluding the mobilityControlInfo (handover). The SCell(s) may bechanged using the RRC Connection Reconfiguration message either with orwithout the mobilityControlInfo. The network may trigger the handoverprocedure e.g. based on radio conditions, load, QoS, UE category, and/orthe like. To facilitate this, the network may configure the UE toperform measurement reporting (possibly including the configuration ofmeasurement gaps). The network may also initiate handover blindly, forexample without having received measurement reports from the UE. Beforesending the handover message to the UE, the source eNB may prepare oneor more target cells. The source eNB may select the target PCell. Thesource eNB may also provide the target eNB with a list of best cells oneach frequency for which measurement information is available, forexample, in order of decreasing RSRP. The source eNB may also includeavailable measurement information for the cells provided in the list.The target eNB may decide which SCells are configured for use afterhandover, which may include cells other than the ones indicated by thesource eNB.

In an example, according to some of the various aspects of embodiments,the target eNB may generate a message used to configure the UE for thehandover, for example, the message including the access stratumconfiguration to be used in the target cell(s). The source eNB maytransparently (for example, does not alter values/content) forward thehandover message/information received from the target eNB to the UE.When appropriate, the source eNB may initiate data forwarding for (asubset of) the dedicated radio bearers. After receiving the handovermessage, the UE may attempt to access the target PCell at the availableRACH occasion according to a random access resource selection. Whenallocating a dedicated preamble for the random access in the targetPCell, E-UTRA may ensure the preamble is available from the first RACHoccasion the UE may use. Upon successful completion of the handover, theUE may send a message used to confirm the handover to the target eNB.

In an example, according to some of the various aspects of embodiments,if the target eNB does not support the release of RRC protocol which thesource eNB used to configure the UE, the target eNB may be unable tocomprehend the UE configuration provided by the source eNB. In thiscase, the target eNB may use the full configuration option toreconfigure the UE for handover and re-establishment. Full configurationoption includes an initialization of the radio configuration, whichmakes the procedure independent of the configuration used in the sourcecell(s) with the exception that the security algorithms are continuedfor the RRC re-establishment.

In an example, according to some of the various aspects of embodiments,after the successful completion of handover, PDCP SDUs may bere-transmitted in the target cell(s). This may apply for dedicated radiobearers using RLC-AM mode and/or for handovers not involving fullconfiguration option. After the successful completion of handover notinvolving full configuration option, the SN (sequence number) and/or theHFN (hyper frame number) may be reset for some radio bearers. For thededicated radio bearers using RLC-AM mode both SN and HFN may continue.For reconfigurations involving the full configuration option, the PDCPentities may be newly established (SN and HFN may not continue) fordedicated radio bearers irrespective of the RLC mode. UE behavior to beperformed upon handover may be the same regardless of the handoverprocedures used within the network (e.g. whether the handover includesX2 or S1 signalling procedures).

In an example, the source eNB may, for some time, maintain a context toenable the UE to return in case of handover failure. After havingdetected handover failure, the UE may attempt to resume the RRCconnection either in the source PCell or in another cell using the RRCre-establishment procedure. This connection resumption may succeed ifthe accessed cell is prepared. For example, when the access cell is acell of the source eNB or of another eNB towards which handoverpreparation has been performed. The cell in which the re-establishmentprocedure succeeds becomes the PCell while SCells, if configured, may bereleased.

In an example, normal measurement and mobility procedures may be used tosupport handover to cells broadcasting a CSG (closed subscriber group)identity. In addition, E-UTRAN may configure the UE to report that it isentering or leaving the proximity of cell(s) included in its CSGwhitelist. E-UTRAN may request the UE to provide additional informationbroadcast by the handover candidate cell e.g. cell global identity, CSGidentity, CSG membership status. E-UTRAN may use the proximity report toconfigure measurements as well as to decide whether or not to requestadditional information broadcast by the handover candidate cell. Theadditional information may be used to verify whether or not the UE isauthorized to access the target PCell and may also be needed to identifyhandover candidate cell. This may involve resolving PCI confusion, forexample, when the physical layer identity that is included in themeasurement report may not uniquely identify the cell.

In an example, according to some of the various aspects of embodiments,configuration of SPS may be configured by the serving eNB with RRCsignalling. The mechanism for SPS configuration and reconfiguration maybe based on RRC signalling. When needed, configuration of SPS may bereconfigured with RRC signalling. In an example, the mapping between anSCell and a SPS may not be reconfigured with RRC while the SCell isconfigured. For example, if there is a need modify SPS configurations,at least one RRC message, for example at least one RRC reconfigurationmessage, may be send to the UE to reconfigure SPS configurations.

In an example, according to some of the various aspects of embodiments,when an eNB performs Cell addition configuration, the related SPSconfiguration may be configured for the Cell. The eNB may modify SPSconfiguration of a cell by removing (releasing) the cell and adding anew cell (with same physical cell ID and frequency) with an updated SPS(e.g. updated SPS ID). The new Cell with the updated SPS may beinitially inactive subsequent to joining the updated SPS. The eNB mayactivate the updated new SCell and/or start scheduling packets on theactivated SCell.

In an example, according to some of the various aspects of embodiments,an eNB may consider UE's capability in configuring one or more SPS for aUE. A UE may be configured with a configuration that is compatible withUE capability. Enhanced SPS capability may be an optional feature in LTErelease 14 (and/or beyond). The UE may transmit its SPS capability to aserving eNB via an RRC message and eNB may consider the UE capability inconfiguring SPS configuration.

In an example, according to some of the various aspects of embodiments,a UE may transfer to an eNB assistance information that the receivingeNB may consider when configuring an SPS configuration for the UE. Themechanism for transferring UE assistance information may be based on RRCsignaling and/or MAC signaling. In an example, an RRC signaling message(e.g. UEAssistanceInformation message) and/or a MAC CE message (MACsignaling message) may be used to transfer UE assistance information forSPS configuration from a UE to an eNB.

In an example, the purpose of RRC connection reconfiguration proceduremay be to modify an RRC connection, e.g. to establish, modify and/orrelease RBs, to perform handover, to setup, modify, and/or releasemeasurements, to add, modify, and/or release SCells. As part of theprocedure, NAS dedicated information may be transferred from E-UTRAN tothe UE. If the received RRC Connection Reconfiguration message includesthe sCellToReleaseList, UE performs SCell release. If the received RRCConnection Reconfiguration message includes the sCellToAddModList, UEperforms SCell additions or modification.

In an example, the UE context within the source eNB may containinformation regarding roaming/handover restrictions which may beprovided either at connection establishment or at the last TA (trackingarea) update process. The source eNB may configure the UE measurementprocedures employing at least one RRC connection reconfigurationmessage. The UE may be triggered to send at least one measurement reportby the rules set by, for example, system information, RRC configuration,and/or the like. The source eNB may make a handover decision based onmany parameters, for example, the measurement reports, RRM information,traffic and load, a combination of the above, and/or the like. Thesource eNB may initiate the handover procedure by sending a handoverrequest message to one or more potential target eNBs. When the sourceeNB sends the handover request message, it may start a handoverpreparation timer. Upon reception of the handover requestacknowledgement message the source eNB may stop the handover preparationtimer.

In an example, in an X2 handover process in FIG. 10 , the source eNB maytransmit a handover request message to one or more potential target eNBpassing information to prepare the handover at the target side. Thehandover request message may comprise SPS capability information of theUE. In an example embodiment, handover request message may furthercomprise the current SPS configuration of the UE connected to theserving eNB. In an example embodiment, the handover request message mayfurther comprise the UE assistance information received from the UE forSPS configuration. In an example, an RRC Context IE in the handoverrequest message may contain the SPS capability information, the currentSPS configuration, and/or the UE assistance information. In an example,an as-Context IE in the HandoverPreparationInformation message (RRCContext IE in the handover request message) may contain the UEassistance information.

In an example, in an S1 handover process without MME relocation in FIG.11 , the source eNB may transmit a handover required message to an MMEfor one or more potential target eNB, and the MME may transmit ahandover request message to the potential target eNBs. The handoverrequired message, and/or the handover request message may passinformation to prepare the handover at the target side. The handoverrequired message, and/or the handover request message may comprise SPScapability information of the UE, the current SPS configuration of theUE in the serving eNB, and/or UE assistance information received fromthe UE for SPS configuration. In an example, a Source to TargetTransparent Container IE in the handover required message and/or thehandover request message may contain the SPS capability information, thecurrent SPS configuration, and/or the UE assistance information.

In an example, in an S1 handover process relocating an MME in FIG. 12 ,the source eNB may transmit a handover required message to a source MMEfor one or more potential target eNB, the source MME may transmit aforward relocation request message to one or more potential target MMEsserving the potential target eNBs, and the potential target MMEs maytransmit a handover request message to the potential target eNBs. Thehandover required message, the forward relocation request message,and/or the handover request message may pass information to prepare thehandover at the target side. The handover required message, the forwardrelocation request message, and/or the handover request message maycomprise SPS capability information of the UE, the current SPSconfiguration of the UE in the serving eNB, and/or UE assistanceinformation received from the UE for SPS configuration. In an example, aSource to Target Transparent Container IE in the handover requiredmessage and/or the handover request message may contain the SPScapability information, the current SPS configuration, and/or the UEassistance information. In an example, an E-UTRAN Transparent ContainerIE in the forward relocation request message may contain the SPScapability information, the current SPS configuration, and/or the UEassistance information.

In an example, during the handover preparation phase, the serving eNBmay transmit UE's SPS capability, UE's current SPS configuration (SPS ofthe UE in connection with the serving eNB), and/or UE assistanceinformation received from the UE for SPS configuration to one or morepotential target eNBs. This information may be employed, at least inpart, by the potential target eNB to configure the UE, for example, toconfigure SPS configuration parameters that may be employed aftercompleting the handover.

In an example, the target eNB may employ the SPS capability, the SPSconfiguration (SPS of the UE in connection with the serving eNB) and/orUE assistance information of the UE in order to properly configure SPSconfiguration of the UE before UE connects to the target UE. The targeteNB may configure the UE considering the SPS configuration limitationsand capabilities of the UE. For example, if the UE does not support SPScapability, the target eNB may not configure the UE with SPS(s). Inanother example, a UE may not support SPS configuration, and eNB mayconsider this in configuring the UE before the UE accesses the targeteNB.

In an example, handover admission control may be performed by the targeteNB dependent on many factors, for example, QoS required for the UEbearers, UE capabilities, UE configuration, target eNB load, acombination of the above, and/or the like. The target eNB may configurethe required resources according to the received information from theserving eNB and may reserve a C-RNTI and/or a RACH preamble. The accessstratum configuration to be used in the target cell may be specifiedindependently (for example as an establishment) or as a delta comparedto the access stratum-configuration used in the source cell (for exampleas a reconfiguration).

In an example, the target eNB may prepare handover with L1/L2 and maysend the handover request acknowledge message to the source eNB. In anX2 handover procedure, the handover request acknowledge message mayinclude a transparent container to be sent to the UE as an RRC messageto perform the handover. In an S1 handover procedure without MMErelocation, the handover request acknowledge message from the target eNBto the MME and/or the handover command message from the MME to thesource eNB may include a transparent container to be sent to the UE asan RRC message to perform the handover. In an S1 handover procedurerelocating an MME, the handover request acknowledge message from thetarget eNB to the target MME, the forward relocation response messagefrom the target MME to the source MME, and/or the handover commandmessage from the source MME to the source eNB may include a transparentcontainer to be sent to the UE as an RRC message to perform thehandover. The container may include a new C-RNTI, target eNB securityalgorithm identifiers for the selected security algorithms, a dedicatedRACH preamble, access parameters, SIBs, and/or other configurationparameters. The transparent container may further comprise the SPSconfigurations for connection of the UE to the target eNB. The SPSconfigurations may modify the SPS of the UE or may keep the same SPSconfiguration that the UE has with the serving base station. The targeteNB may generate the RRC message to perform the handover, for example,RRC connection reconfiguration message including the mobility controlinformation. The RRC message may be sent by the source eNB towards theUE.

In an example, the source eNB may perform the necessary integrityprotection and ciphering of the message. The UE may receive the RRCconnection reconfiguration message from the source eNB and may startperforming the handover. The UE may not need to delay the handoverexecution for delivering the HARQ/ARQ responses to the source eNB.

In an example, after receiving the RRC connection reconfigurationmessage including the mobility control information, UE may performsynchronisation to the target eNB and accesses the target cell via RACHon the primary cell. The UE Random access procedure may employ acontention-free procedure if a dedicated RACH preamble was indicated inthe mobility control information. The UE random access procedure mayemploy a contention-based procedure if no dedicated preamble wasindicated. The UE may derive target eNB specific keys and may configurethe selected security algorithms to be used in the target cell. Thetarget eNB may respond with uplink allocation and timing advance.

In an example, after the UE has successfully accessed the target cell,the UE may send an RRC connection reconfiguration complete message(C-RNTI) to confirm the handover and to indicate that the handoverprocedure is completed for the UE. UE may transmit a MAC uplink BufferStatus Report (BSR) Control Element (CE) along with the uplink RRCConnection Reconfiguration Complete message or may transmit a MAC uplinkBSR CE whenever possible to the target eNB. UE may transmit, along withthe uplink RRC Connection Reconfiguration Complete message, UEassistance information that the receiving eNB may consider whenconfiguring an SPS configuration for the UE. In an example, a MAC CEmessage may contain the UE assistance information for an SPSconfiguration for the UE in the target eNB. The target eNB verifies theC-RNTI sent in the RRC Connection Reconfiguration Complete message. Thetarget eNB may now begin sending data to the UE and receiving data fromthe UE.

In an example, after receiving the RRC Connection ReconfigurationComplete message, the target eNB may activate one or more SPSs that wasconfigured by the target eNB during the handover preparation procedure.In an example, the target eNB may use the information in the UEassistance information (e.g., message size, periodicity, timing offset,e.g., offset to subframe 0 of SFN0) to determine the next packetgeneration time by the UE. In an example, the target eNB may considerthe message size information in the UE assistance information todetermine the grant size in the SPS activation DCI.

In an example, the target eNB may determine the next packet generationtime employing the UE assistance information. For example, the targeteNB employs offset information (e.g. offset to SF0 of SFN0, or otheroffset information fields) and/or period in the assistance informationto determine a next packet generation time. In an example, the nextpacket generation time is a first subframe after receiving the RRCconnection reconfiguration complete message.

In an example, after receiving the RRC Connection ReconfigurationComplete message, the target eNB may consider the next packet generationtime and send the DCI for SPS activation k subframes (e.g. k=4) earlierthan the next packet generation time. In an example k may depend onframe structure type, e.g. TDD vs. FDD. For TDD frame structure type, kmay depend on the subframe number and TDD configuration.

In an example, the target eNB may consider the first packet generationtime which occurs k subframes (e.g. k=4) or later after the target eNBreceives the RRC Connection Reconfiguration Complete message and maysend the SPS activation DCI k subframes (e.g. k=4) earlier than thatsubframe. In an example, target eNB may transmit the SPS activation DCIafter the target eNB receives the RRC Connection ReconfigurationComplete message (e.g., immediately) and the UE may use the grant at theappropriate packet generation times.

In an example, according to some of the various aspects of embodiments,a serving base station may receive a first message from a wirelessdevice on a primary cell in a plurality of cells. The first message maybe an RRC UE capability message. The plurality of cells may comprise theprimary cell and at least one secondary cell. The first message maycomprise at least one parameter indicating whether the wireless devicesupports configuration of SPS(s). The base station may receive aplurality of radio capability parameters from the wireless device.

In an example, according to some of the various aspects of embodiments,a serving base station may receive a first message from a wirelessdevice on a primary cell in a plurality of cells. The first message maybe an RRC signaling message (e.g. a UE AssistanceInformation message)and/or a MAC CE message. The plurality of cells may comprise the primarycell and at least one secondary cell. The first message may comprise atleast UE assistance information that a base station may consider whenthe base station configures SPS configurations for the UE. The basestation may receive a plurality of UE assistance information from thewireless device.

In an example embodiment, the capability message may comprise one ormore parameters explicitly and/or implicitly indicating that the UEsupport configuration of SPS. For example, a parameter may indicate thatthe UE is capable of handling some types of V2X configuration, and thismay imply that the UE is SPS capable. In an example, a parameter mayindicate that the UE is capable of supporting a set of enhancedconfiguration parameters including enhanced SPS (e.g. SPS). In anexample, a parameter may explicitly indicate that the UE is capable ofhandling enhanced SPS configuration. The eNB after receiving the UEcapability message, may determine whether the UE can supportconfiguration of enhanced SPS (SPS). The UE may selectively configureSPS for a UE by transmitting one or more RRC messages to the UE. In anexample embodiment, the capability may be received on a first signallingbearer on the primary cell. The plurality of radio capability parametersmay comprise a first sequence of one or more radio configurationparameters. A first radio configuration parameter in the first sequencemay comprise a first parameter indicating whether SPS may be supportedfor a first band and/or first band combination. The first band and/orfirst band combination may be in a second sequence of one or more bandcombinations. The index of the first radio configuration parameter inthe first sequence may determine the index of the first band combinationin the second sequence.

In an example, according to some of the various embodiments, the size ofthe first sequence may be the same as the size of the second sequence.The index may determine the order of: the first radio configurationparameter in the first sequence; and the first band combination in thesecond sequence. The first band combination may be identified by a firstband combination parameter. The first band combination parameter maycomprise a list of band identifier(s). Each of the band identifier(s)may be one of a finite set of numbers. Each of the numbers may identifya specific band.

In an example, according to some of the various embodiments, thewireless device may support one or more inter-band SPSs if the list ofband identifier(s) includes more than one band; and the first parameterindicates that SPS is supported. In yet other embodiments, the wirelessdevice may support multiple intra-band SPS if the list of bandidentifier(s) includes one band; and the first parameter indicates thatSPS is supported.

In an example, according to some of the various embodiments, thewireless device may not support SPS if none of the radio configurationparameters comprise a parameter indicating that SPS is supported.

In an example embodiment, a wireless device may transmit an RRC messagecomprising UE capability information. The UE capability information maycomprise one or more information elements comprising wireless device LTEradio capability parameters. The LTE radio capability parameters maycomprise a plurality of parameters indicating various capability of thewireless device LTE radio.

In an example, the serving base station may selectively transmit atleast one second message to the wireless device if the at least oneparameter indicates support for configuration of SPS. The at least onesecond message may configure SPS in the wireless device. If the at leastone parameter does not indicate support for configuration SPS, the basestation may not configure SPS in the wireless device. If the at leastone parameter indicates support for configuration of the SPS, the basestation may or may not configure SPS in the wireless device depending onthe required wireless device configuration and many other parameters,such as types of application running on the UE and the trafficrequirements. Transmission or not transmission (selective transmission)of at least one second message to configure SPS is determined by thebase station based on many criteria described in this specification.

In an example, the at least one second control message may be configuredto cause in the wireless device configuration of at least one cell inthe plurality of cells and configuration of SPS. The first SPS maycomprise a first subset of the plurality of cells. The second SPS maycomprise a second subset of the at least one secondary cell.

In an example, the at least one second control message may be configuredto further cause in the wireless device configuration of one or more SPSconfiguration. A cell add-modify information element may comprise afirst plurality of dedicated parameters. The first plurality ofdedicated parameters may comprise a first cell index for a firstsecondary cell in the at least one secondary cell. The at least onesecond control message may further include configuration information forphysical channels for the wireless device. The at least one secondcontrol message may be configured to further cause the wireless deviceto set up or modify at least one radio bearer.

In an example, the serving base station may receive at least onemeasurement report from the wireless device in response to the at leastone second message. The at least one measurement report may comprisesignal quality information of at least one of the at least one cell ofat least one of the at least one target base station. The signal qualityinformation may be derived at least in part employing measurements of atleast one OFDM subcarrier. The serving base station may make a handoverdecision, based, at least in part, on the at least one measurementreport, and/or other parameters, such as load, QoS, mobility, etc. Theserving base station may also make a decision depending on base stationinternal proprietary algorithm.

In an example, the serving base station may transmit at least one thirdmessage to at least one of the at least one target base station. The atleast one third message may comprise the at least one parameterindicating whether the wireless device supports configuration of SPS.The at least one third message may comprise a plurality of parameters ofthe configuration at least indicating association between at least onecell and a corresponding SPS (configuration information of one or moreSPSs). The at least one third message may be a handover request messagetransmitted to at least one target base station to prepare the targetbase stations for the handover of the wireless device. The UE capabilityparameters may be included in the at least one third message. UEdedicated radio parameters comprising UE SPS configuration may also beincluded in the handover request message. UE dedicated radio parametersmay comprise MACMainconfig information element. UE dedicated radioparameters may comprise SPS configuration including SPS indices andassociated cell indices.

In an example, according to some of the various aspects of embodiments,a serving base station, in response to making a handover decision by theserving base station for a wireless device, may transmit at least onethird message to at least one target base station. The at least onethird message may comprise the at least one parameter indicating whetherthe wireless device supports configuration of SPS. The format of theparameter (information element) indicating whether the wireless devicesupports configuration of a SPS is the same format as the UE capabilitymessage transmitted by the wireless device to the base station in thefirst message as described in the specification. The at least one thirdmessage may further comprise a plurality of parameters of theconfiguration of SPS (configuration information of SPS). The parametersincluded in the configuration information of SPS may be the same as theones included in the at least one second message as described in thisspecification. The at least one third message may be a handover requestmessage transmitted to at least one target base station to prepare thetarget base stations for the handover of the wireless device. The UEcapability parameters may be included in the at least one third message.UE dedicated radio parameters comprising UE SPS configuration may alsobe included in the handover request message. UE dedicated radioparameters may comprise MACMainconfig information element. UE dedicatedradio parameters may comprise SPS configuration including SPS indicesand associated cell indices.

In an example, the serving base station may receive from one of the atleast one target base station at least one fourth message. The at leastone fourth message may comprise configuration of a plurality of cellsfor the wireless device. The plurality of cells may comprise a primarycell and at least one secondary cell. The configuration may associateSPS configuration with a cell in the plurality of cells.

In an example, the serving base station may transmit a fifth message tothe wireless device. The fifth message may comprise a plurality ofparameters of the configuration at least indicating association betweenat least one cell and a corresponding SPS (configuration information ofSPS). The fifth message may cause the wireless device to start asynchronization process with the target base station (with a cell in thetarget base station).

In an example, the base station may, before transmission of the fifthmessage, encrypt the fifth message and protect the fifth message by anintegrity header. The fifth message may further include configurationinformation for physical channels for the wireless device. The fifthmessage may be configured to cause the wireless device to set up ormodify at least one radio bearer. The fifth message may be configured tofurther cause the wireless device to configure at least one of aphysical layer parameter, a MAC layer parameter, and an RLC layerparameter. The plurality of cells of the target base station may be inmore than one frequency band, for example, one or more cells may be infrequency band A and one or more other cells may be in frequency band B(inter-band carrier aggregation). The wireless device may supportconfiguration of SPS.

In an example, a source base station may transmit, to a target basestation, a first message comprising assistance information. Theassistance information may comprise one or more fields indicating atleast one of semi-persistent scheduling (SPS) periodicity, SPS messagesize or SPS timing offset. The target base station may transmit, to thesource base station, a second message comprising one or more SPSconfiguration parameters. At least one of the one or more SPSconfiguration parameters may be determined by target base station atleast based on the assistance information. The source base station maytransmit, to a wireless device, a third message comprising the SPSconfiguration parameters.

In an example, the target base station may transmit, to the wirelessdevice, an SPS activation downlink control information (DCI). The SPSactivation DCI may comprise a grant size determined based on the SPSmessage size. In an example, the target base station may transmit, tothe wireless device, an SPS activation downlink control information(DCI) in a subframe determined at least based on the UE assistanceinformation.

In an example, a wireless device may transmit, to a target base station,a random access preamble during a handover procedure. The wirelessdevice may receive, from the target base station, a random accessresponse (RAR) message. The RAR message may comprise a grant for thewireless device. The wireless device may transmit, to the target basestation, a third message comprising assistance information. Theassistance information may comprise at least one of semi-persistentscheduling (SPS) periodicity, SPS message size, and/or SPS timingoffset.

In an example, the target base station may transmit, to the wirelessdevice, an SPS activation downlink control information (DCI) comprisinga grant size, the grant size determined based on the SPS message size.In an example, the target base station may transmit, to the wirelessdevice, an SPS activation downlink control information (DCI) in asubframe determined at least based on the UE assistance information.

In an example, SPS radio resources comprise SPS resource, SPS resourceconfigurations, and/or the like. An SPS activation control command maycomprise an SPS activation command, an SPS activation message, an SPSactivation indication, and/or the like. In an example, SPS traffic maycomprise SPS data, SPS packets, SPS traffic packets, V2X data, V2Xpackets, periodic data, periodic packets, and/or the like. A periodicitymay comprise a time duration, a number of subframes, an absolute timevalue, a relative time value, and/or the like. An offset may comprise arelative time value (e.g. −1, −2, +1, +3, and/or the like).

According to various embodiments, a device (such as, for example, awireless device, an off-network wireless device, a base station, and/orthe like), may comprise, for example, one or more processors and memory.The memory may store instructions that, when executed by the one or moreprocessors, cause the device to perform a series of actions. Embodimentsof example actions are illustrated in the accompanying figures andspecification. Features from various embodiments may be combined tocreate yet further embodiments.

FIG. 15 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 1510, a first base station may receive arequest message for a handover of a wireless device from a second basestation. The request message may comprise traffic pattern parameters forone or more semi-persistent scheduling (SPS) traffic of the wirelessdevice. The traffic pattern parameters may comprise: a first trafficperiodicity of a first traffic of the one or more SPS traffic; a firsttiming offset of the first traffic; and a first message size of thefirst traffic. At 1520, the first base station may determine, based atleast on the traffic pattern parameters, at least one SPS configurationparameter for SPS radio resources. At 1530, the first base station maysend a handover request acknowledge message to the second base station.The handover request acknowledge message may indicate the at least oneSPS configuration parameter. At 1540, the first base station may receivea random access (RA) preamble from the wireless device. The RA preamblemay be associated with the handover of the wireless device. At 1550, asubframe in a plurality of subframes based at least on the trafficpattern parameters may be determined. At 1560, the first base stationmay transmit, to the wireless device, an SPS activation control commandin the subframe indicating activation of the SPS radio resources.

According to an embodiment, the second base station may receive thetraffic pattern parameters from the wireless device via a UE assistanceinformation message. According to an embodiment, the second base stationmay transmit to the wireless device, a handover command messageindicating the at least one SPS configuration parameter in response toreceiving the handover request acknowledge message. According to anembodiment, the at least one SPS configuration parameter may comprise anSPS periodicity for the SPS radio resources. According to an embodiment,the SPS activation control command may comprise a resource blockassignment determined based on the first message size. According to anembodiment, the transmitting of the SPS activation control command maybe after a transmission of an RA response message in response to the RApreamble. According to an embodiment, the transmitting of the SPSactivation control command may be via a downlink control information.

FIG. 16 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 1610, a first base station may receive a UEassistance information message from a wireless device. The UE assistanceinformation message may comprise traffic pattern parameters for one ormore SPS traffic of the wireless device. The traffic pattern parametersmay comprise: a first traffic periodicity of a first traffic of the oneor more SPS traffic; a first timing offset of the first traffic; and afirst message size of the first traffic. At 1620, the first base stationmay send, to a second base station, a request message for a handover ofthe wireless device. The request message may comprise the trafficpattern parameters. At 1630, the first base station may receive from thesecond base station, a handover request acknowledge message indicatingat least one SPS configuration parameter for SPS radio resourcesdetermined based at least on the traffic pattern parameters. At 1640,the first base station may transmit to the wireless device, a handovercommand message indicating the at least one SPS configuration parameter.

According to an embodiment, the at least one SPS configuration parametermay comprise an SPS periodicity for the SPS radio resources. Accordingto an embodiment, the second base station may receive from the wirelessdevice, a random access (RA) preamble associated with the handover ofthe wireless device. According to an embodiment, a subframe in aplurality of subframes may be determined based at least on the trafficpattern parameters. According to an embodiment, the second base stationmay transmit to the wireless device, an SPS activation control commandin the subframe indicating activation of the SPS radio resources.According to an embodiment, the SPS activation control command maycomprise a resource block assignment determined based on the firstmessage size. According to an embodiment, the transmission of the SPSactivation control command may be after a transmission of an RA responsemessage in response to the RA preamble. According to an embodiment, thetransmission of the SPS activation control command may be via a downlinkcontrol information.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, MATLAB or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using FDD communication systems. However, one skilled in the art willrecognize that embodiments of the invention may also be implemented in asystem comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 3-licensed assisted access). The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112, paragraph 6. Claims that do not expressly include the phrase“means for” or “step for” are not to be interpreted under 35 U.S.C. 112.

1. A method comprising: receiving, by a first base station from a secondbase station, a handover request message comprising traffic patternparameters of a wireless device, the traffic pattern parameterscomprising a first traffic periodicity, a first timing offset, and afirst message size; sending, to the second base station, a handoverrequest acknowledge message indicating at least one periodic resourceconfiguration parameter determined based on the first trafficperiodicity; receiving, from the wireless device, a random accesspreamble associated with a handover of the wireless device; determining,by the first base station, a resource block assignment based on thefirst message size; and transmitting, to the wireless device, a controlcommand indicating: activation of radio resources associated with the atleast one periodic resource configuration parameter; and the resourceblock assignment.
 2. The method of claim 1, further comprisingreceiving, by the second base station, the traffic pattern parametersfrom the wireless device via an assistance information message.
 3. Themethod of claim 1, further comprising sending, by the second basestation to the wireless device, a handover command message indicatingthe at least one periodic resource configuration parameter in responseto receiving the handover request acknowledge message.
 4. The method ofclaim 1, wherein the at least one periodic resource configurationparameter comprises a resource periodicity.
 5. The method of claim 1,wherein the transmitting of the control command is after a transmissionof a random access response message in response to the random accesspreamble.
 6. The method of claim 1, wherein the transmitting of thecontrol command comprises transmitting the control command at anactivation timing determined based on the first timing offset.
 7. Themethod of claim 1, wherein the transmitting the control command is via adownlink control information.
 8. A first base station comprising: one ormore processors; memory storing instructions that, when executed by theone or more processors, cause the first base station to: receive, from asecond base station, a handover request message comprising trafficpattern parameters of a wireless device, the traffic pattern parameterscomprising a first traffic periodicity, a first timing offset, and afirst message size; send, to the second base station, a handover requestacknowledge message indicating at least one periodic resourceconfiguration parameter determined based on the first trafficperiodicity; receive, from the wireless device, a random access preambleassociated with a handover of the wireless device; determine a resourceblock assignment based on the first message size; and transmit, to thewireless device, a control command indicating: activation of radioresources associated with the at least one periodic resourceconfiguration parameter; and the resource block assignment.
 9. The firstbase station of claim 8, wherein the second base station receives thetraffic pattern parameters from the wireless device via an assistanceinformation message.
 10. The first base station of claim 8, wherein thesecond base station sends, to the wireless device, a handover commandmessage indicating the at least one periodic resource configurationparameter in response to receiving the handover request acknowledgemessage.
 11. The first base station of claim 8, wherein the at least oneperiodic resource configuration parameter comprises a resourceperiodicity.
 12. The first base station of claim 8, wherein theinstructions that cause the base station to transmit the control commandafter a transmission of a random access response message in response tothe random access preamble.
 13. The first base station of claim 8,wherein the instructions that cause the base station to transmit thecontrol command further comprise instructions that cause the basestation to transmit the control command at an activation timingdetermined based on the first timing offset.
 14. The first base stationof claim 8, wherein the control command is transmitted is via a downlinkcontrol information.
 15. A method comprising: receiving, by a first basestation from a wireless device, an assistance information messagecomprising traffic pattern parameters of the wireless device, thetraffic pattern parameters comprising a first traffic periodicity, afirst timing offset, and a first message size; sending, to a second basestation, a handover request message comprising the traffic patternparameters of the wireless device, wherein the traffic patternparameters enable the second base station to determine a subframe in aplurality of subframes for transmission of an control command to thewireless device based on the first traffic periodicity and the firsttiming offset; receiving, from the second base station, a handoverrequest acknowledge message indicating at least one periodic resourceconfiguration parameter for radio resources determined based on thetraffic pattern parameters; and transmitting, to the wireless device, ahandover command message indicating the at least one periodic resourceconfiguration parameter.
 16. The method of claim 15, wherein the atleast one periodic resource configuration parameter comprises a resourceperiodicity.
 17. The method of claim 15, further comprising: receiving,by the second base station from the wireless device, a random accesspreamble associated with a handover of the wireless device; determining,by the second base station, a resource block assignment based on thefirst message size; and transmitting, by the second base station to thewireless device, the control command indicating: activation of the radioresources associated with the at least one periodic resourceconfiguration parameter; and the resource block assignment.
 18. Themethod of claim 17, wherein the transmitting of the control command isafter a transmission of a random access response message in response tothe random access preamble.
 19. The method of claim 17, wherein thetransmitting of the control command comprises transmitting the controlcommand at an activation timing determined based on the first timingoffset.
 20. The method of claim 17, wherein the transmitting of thecontrol command is via a downlink control information.